BP: Removal of CL_CMD_APPLLOG=>GET_SINGLETON_INSTANCE usages
[application] [AUnit-scenarios] [BANK_DETAILS] [BUPA] [Business] [BUSINESS_PARTNER] [BUSINESS_PARTNER_TMPL] [CL_BUP_BANK_ESA] [CL_BUP_CARD_1] [CL_CMD_APPLLOG] [CL__BUP_TRANSACTION_PARTNER] [CONSTRUCTOR] [different] [drm removal kit] [GET_SINGLETON_INSTANCE] [in] [instances] [log] [of] [Partner] [PAYMENT_CARD_DETAILS] [removal] [removal tool] [speckle removal]
Related:
- BUPA_DESCRIPTION_GET does not return long name descriptionSymptom The function module BUPA_DESCRIPTION_GET returns only the short name...
- SAP BP: R11 244 when a BP is displayedSymptom Even though a Business Partner does not have any...
- All Offsetting accounts should be displayed in GL reportSymptom All GL offsetting account or counter account should be...
- BP_SEA Missing entries in TPZ1; phonetic search incorrectSymptom You use the phonetic search (BDT search help). However,...
- Short dump when changing name of business partnerSymptom You create a business partner with an address that...
- Exemption Values are not showing in TTE Display DocumentSymptom Open a Sales Order in CRM system ,go to...
- Secure handling of credit card data in ERPSymptom Secure handling of credit card data in ERP Other...
- Scheduling of MDRO in ByD BCDT systemsSymptom MDRO ( Mass Data Run Objects ) are scheduled...
Symptom
Obsolete instance handling of application log (CL_CMD_APPLLOG) in BankDetails- and PaymentCardDetails-IPI has to be swapped to the new concept.
Other terms
BUSINESS_PARTNER_TMPL, BUSINESS_PARTNER, BANK_DETAILS, PAYMENT_CARD_DETAILS, BuPa, Business Partner, CL_CMD_APPLLOG, application log, GET_SINGLETON_INSTANCE, CL_BUP_CARD_1, CL_BUP_BANK_ESA, CONSTRUCTOR, CL__BUP_TRANSACTION_PARTNER, different instances of application log in AUnit-scenarios
Reason and Prerequisites
With this correction this functional adaptation is done as required by the new concept (do not use CL_CMD_APPLLOG=>GET_SINGLETON_INSTANCE anymore BUT get the APPLLOG instance now from the transactional class CL_BUP_TRANSACTION_PARTNER).
The change is functional currently only necessary in AUnit-scenarios, since up to now the same singleton instance is used in the transactional class as derived by the old method.
Solution
Problem is solved with ByD FP2.5.