Scribd
Upload
273 views2 pages

FK08 Issue

The document discusses an issue with updating bank information like IBAN in SAP when using business processes. Specifically: 1) When an IBAN is changed in a business process, the payment block is not correctly set, even after multiple changes to the IBAN. 2) Debugging showed the old and new IBAN data is written to attributes in the VMD_EI_API_MEMORY class but the data synchronization does not detect the change. 3) The customer requests possible extension points like user exits or BAdIs where they could intervene to address the issue.

Uploaded by

Subhasis Jethy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
273 views2 pages

FK08 Issue

The document discusses an issue with updating bank information like IBAN in SAP when using business processes. Specifically: 1) When an IBAN is changed in a business process, the payment block is not correctly set, even after multiple changes to the IBAN. 2) Debugging showed the old and new IBAN data is written to attributes in the VMD_EI_API_MEMORY class but the data synchronization does not detect the change. 3) The customer requests possible extension points like user exits or BAdIs where they could intervene to address the issue.

Uploaded by

Subhasis Jethy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

0120025231 0000144311 2013 0120050409 0000058599 2012 Note 827991 note 1604004 V_T055F -to mark the sesitive

field. USER--ZUGANGSAP PASS--test456 ++++++++++++++++++++++++++++++++++++++++++++++++++++ Vergenie ----------We need it because once in CVI - after the BP POC (Perform On Commit) TIBAN database modify already occured and associated memory in SAPLIBMA (cf xtiban[] ytiban[]) is already overwritten/cleared. You can check this from cvi_mapper=>map_bps_to_customers and from cmd_ei_api->maintain_single (resp. vmd_ei_api) but old values are not there anymore (cf (SAPLIBMA)xtiban[] ytiban[]). This should not be change, it is ok, because we TIBAN twice. Nevertheless, in context of BP, we -tion for sensitive fields. Ideally this should for all tables/fields not duplicated between BP master data). should not update need additional informabe generalized data and customer/vendor

For testing I used Q35/002 with BP->customer VL_CUST2. Scenario is to change only the IBAN (cf change docs for values to test for account DE 99999999 1111111112). At the moment it dumps but you can check debug till cmd_ei_api and after dump all data are back as before (even BP and TIBAN). So easy to test quickly with this example. You can use it. ++++++++++++++++++++++++++++++++++++++++ customer reply ------------------------Call transaction BP -> changing of the IBAN of a bank information -> save -> result: Payment block is not set -> again changing of the IBAN without abandonment of the transaction -> save -> result: Payment block is set. If once again the transaction is always called before the changing, however, a payment block is never set. With that debug the facts' is like, that in the method WRITE_INTO_CURRENT_MEMORY of the class VMD_EI_API_MAP_STRUCTURE the IBAN data (old and new) is written to the class VMD_EI_API_MEMORY into the attributes (GT_CURRENT_IBAN_OLD and GT_CURRENT_IBAN_NEW). Later the data synchronization takes place then on changes. The transaction will not leave, then the two attributes differ after change to the IBAN, the transaction becomes, however, also the changed values are newly called in the attribute GT_CURRENT_IBAN_OLD and thus no payment block is set. This behavior shows us, however, possibly that the function is presumably in principle intended afflicted still with errors is. It would be nice if you could have a closer look at the facts again. A

system access should be necessary, please contact us (see below). No solution should be able to be provided for your part, we are a customer-specific solution so in an inwait way for these facts move. Can they us for the case please suitable positions (User exit, BAdI, and so on) specify, at which we the possibility, have to intervene.

IBAN ----DE64500100600050643602 DE30290800100103742000 VMD_EI_API====================CM022 Program VMD_EI_API====================CM00E line 211 IBAN T055F

You might also like