Inbound IDOC for Invoice failing at segment-E1EDK28- Incorrect BankAccNumbe

[Former Member]

Hi SDNers,

We have EDI - Invoice/Invoice Processing.

Inbound Idoc failing at segment E1EDk28.

This is because in segment E1EDK28 ,

1. The field ACNUM has the value for Bank Account Number as N111111A.

2. This is incorrect.

3. This field should have had the value for account number as 0000N111111A.

4. But for some reason the pre-zerou2019s are removed .

5. When we check the process code IDOC_INPUT_INVOIC_FI, and IDOC_INPUT_INVOIC_MM, and the table LFBK the value is saved as 0000N111111A.

But why in IDOC it is getting seen as N111111A?

Please guide as to where i need to look for the solution or fix.

Where should i look for the fix for this issue.

Regards,

SuryaD.

Edited by: SuryaD on Nov 24, 2009 7:01 PM

Edited by: SuryaD on Nov 25, 2009 9:21 AM

[Former Member]

The type of ACNUM in E1EDK28 is CHAR 30

ACNUM EDI3194LA CHAR 30

The type of ACNUM in LFBK is CHAR 40

EBPP_ACCNAME EBPP_ACCNAME CHAR 40

Hence the difference......

Find in some exit where you can change the values for ACNUM reading the segment : E1EDK28

EXIT_SAPLIEDI_101, EXIT_SAPLIEDI_111, EXIT_SAPLIEDI_102, EXIT_SAPLIEDI_112

[Former Member]

Hi Navitha,

Thanks for your response.

I had checked the exits to see if the field ACNUM is changed anywhere while debugging.

It wasn't getting changed anywhere.

In fact the user and the ticket creator had the assumption that the Vendor Bank Account number (in case of the Inter company billing) is maintained in vendor master (XK03) or LFBK or KNBK.

the y thought IDOC is picking the ACNUM from one of the above three place.

They were checking the Bank account number from the above 3 places and since here it was maintained as 0000N111111A while in IDOC it was showing as N1111111A they had all this confusion.

In fact the IDOC segment E1EDK28 picks the ACNUM from SPRO->Financial Accounting-> Banking->home bank.

Here we checked and found that the Bank Account Number was maintained as N1111111A and we changed it to 0000N1111111A and the IDOc segment E1EDK28 picked it correctly.

Issue got resolved.

Thanks for your input.

Regards,

SuryaD.

Edited by: SuryaD on Nov 25, 2009 10:29 PM

[Former Member]

Resolved .this is an SPRO setting issue.