Skip to Content

E1LFBKM segment not populating in CREMAS IDOC type

Hi Techies,

We are facing an issue with particular one China Bank key, once we are updating the bank details in the Supplier Business partner. E1LBKM segment is not populating in outbound CREMAS IDOC type for production system. But once I am using same bank key in development or quality system, IDOC segment is populating. I am little bit surprised, what would be probable root cause, please help me out.

Regards

J Sen.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Mar 27, 2017 at 12:02 PM

    After you updated your vendor master "with particular one China Bank key" and if you go again in to your vendor master, do you see then your update or is this update not present?

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jurgen,

      I have checked BUT0BK table, I have found that Bank data update for BP but not sync to LFBK table for the particular vendor. Please advice.

  • Mar 27, 2017 at 11:33 AM

    One option is you can compare the same via WE32. The other option is pass that segment in SE11 and from top menu bar, click on Utilities > Versions > Version Management so that you can compare on which date, the segment has been transported. Most probably, some transport request would not have been moved to PRD

    Add comment
    10|10000 characters needed characters exceeded

    • I have checked Lakshmipathi, but issue is that BUT0BK table holds the bank data for BP but that data is not sync up with LFBK table. that is the issue, for that reason IDOC segment is not populating. Now what would be the next step.

      Regards

      J Sen.

  • Mar 27, 2017 at 02:17 PM

    I am not yet used to the new BP transaction. But as far as I know from OSS note 937416 - BP_CVI: Transfer of validity for bank details

    you need a batch input to transfer the data from BUT0BK to LFBK

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 21, 2017 at 07:00 PM

    Have you checked the distribution model is same in DEV and PROD ? Please check BD64

    Add comment
    10|10000 characters needed characters exceeded