However, the two enhancement techniques do differ from each other in the following points: The concepts behind the Business Add-Ins enhancement technique and Open FI are basically the same. pay to hits the books in Accounts Receivable in FI module), whereas the requirement could be to send the same to Bill to party, based on the premise that the original invoice was sent to him as per the partner functions in SD. ![]() For Example: Standard Dunning functionality in SAP sends the notice to the Pay to partner function (based on the partner functions in SD module i.e. This functionality is primarily used in FI in the areas of dunning, credit management, banking etc. ![]() > This can be easily adopted / customized to the business needs wherein SAP does not provide the standard functionality through customization or enhancements. Both industry-specific and country-specific enhancements may be defined. > This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. > Open FI is based upon the following principles: Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically. > The enhancement technique (Open FI) that were developed for Financial Accounting component. ![]() RELATED TRANSACTION CODES.15ĭISCLAIMER AND LIABILITY NOTICE.16 TYPES OF INTERFACES.4įINDING BUSINESS TRANSACTION EVENTS.5īASIC STEPS IN CONFIGURING BUSINESS TRANSACTION EVENTS.5ĮXAMPLE BUSINESS SCENARIO FOR BTE - PROCESS INTERFACE.6 WHAT ARE BUSINESS TRANSACTION EVENTS.3ĭIFFERENCE BETWEEN BADI'S AND BTE'S.3 FI ENHANCEMENT TECHNIQUE – HOW-TO-GUIDE ON THE USAGE OF BUSINESS TRANSACTION EVENTS (BTE).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |