cancel
Showing results for 
Search instead for 
Did you mean: 

Account statement not updated Message no. FB773

gopalrawat
Explorer
0 Kudos

Hello SAP Experts,

I was testing the EBS . While uploading the statement ( format  MT940 86 structured) one of Polish bank.

system is displaying the statement with the message

Account statement not updated

Message no. FB773

Additional information : external transaction is missing in T028G.

All the customization was working good in past, we just created few new external transaction ( 4 digit numeric)

With analysis we come to know that , with above format system is recognizing only ext tran type ( 3 digit numeric)

Does anyone have latest update for the MT940 Format particularly field : 86:

Example : external tran type 9060 is created in

Best Regards

Gopal Rawat

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

first of all, double-check if it's an MT940 with field :86: structured or unstructured. You can do it by checking 4th, 5th and 6th character in any field :86:

For example:

:86:051^00PRZELEW KRAJOWY MI¨DZYBANKO^34000

If 3rd character is a kind of a separator ('^' in the example above, '?', '~' etc.) followed by a 2-digit subfield code ('00' here) it means that field :86: is structured

If there is no such a rule, for example:

:86:401 DEP. PLN; OPROC.: 3.00%; O

field :86: is unstructured.

This implicates the way EBS should be imported and configured. If field :86: is structured, you assign posting rules in table T028G to 3-digit bank transaction codes. If field :86: is unstructured, you use there 4-letter bank transaction codes from field :61: which can be found right after amount:

:61:1001200120DN50000,00NTRFNONREF//MM0924700218;2

Besides, for the latter you use format 'I' in FF_5 whereas for MT940 with field :86: structured you use format 'S'. It might have happened that someone imported MT940 with field 86 unstructured with format S in FF_5. In this case the system took just first 3 characters from field :86: and interpreted it as a bank transaction code.

That's a general rule. However, some enhancement might be in use. Look especially at user exit ZXF01U01 where bank transaction code (FEBEP-VGEXT) and posting rule (FEBEP-VGINT) can be substituted. A lot can happen there.

And one more hint. It's also possible to configure 4-letter bank transaction codes for MT940 with structured field :86:. Let's assume you can find something like this:

:86:012^00WPŁATA ZAMKNIĘTA NA RACHUNE^34002

the bank provided 4-digit bank transaction codes, for example:

0121

0122

0123

etc.

It appears (at least it was like this in my case) that the last 'missing' digit can be found in subfield ^34 (3rd character). Concatenation of bank transaction code 012 from the beginning of field :86: and this digit gives complete bank transaction code.

You just have to populate field FEBEP-VGEXT before interpretation of EBS transaction. To do that, implement BAdI FIEB_CHANGE_BS_DATA.

Tomasz Gerke

gopalrawat
Explorer
0 Kudos

Hi Tomasz,

Thanks for this,

This is really good explanation of information related with EBS , especially format 86 structure and unstructured.    With below data we can see , it is 86 structured <00 ( 5th,6th,7th chars in reocrd :86:

:61:1412161216DN129000,00NERR//0121216608605245

BALANCE CONS TRANSFER

:86:9060<00BALANCE CONS TRANSFER<10

<20Konsolidacja Sald

<27S SP. Z O.O.

<29UL. ½UPNICZA 11 03-821 WARSZAWA PL

<3012406247<311111000049733602

<32S SP. Z O.O.<33

<3856124062471111000049733602

<61

<63REF0121216608605245

Actually 3 digit ext tran code was working fine earlier.

As advised, we need to check the case of format 'I' and format 'S'.  Further it seems we have to resort to user exit here.

Thanks to all. later  I will update the solution got worked in my case.

Regards / Gopal Rawat

Former Member
0 Kudos

Hi,

if you import this one with format 'I', bank transaction code will be extracted from field :61: - NERR. If you use format 'S', bank transaction code will be 906 and subfield separator will be '0' which is something you don't really want as it may lead to short dumps. After import, note to payee data will be shredded.

Check if user exit ZXF01U06 is implemented right now. It may change contents of the imported file.

If I had such a case, I would either use user exit ZXF01U06 to move bank transaction code from field 86 to 61 (replacing NERR) and then import EBS with format 'I' (easy solution), or shift left by one place contents of field :86: after 3-digit bank transaction code, making it:

:86:906<00BALANCE CONS TRANSFER<10

The last digit I would put in additional subfield <34 (this way it would be saved in FEBEP-KKREF). Finally I would implement BAdI I mentioned before to bring them back together and save in FEBEP-VGEXT. This way 4-digit bank transaction codes would be handled and note to payee would stay in place.

Please note that very often users can download EBS in various MT940 sub-formats from the online banking system. It might happen that incorrect (ie. not used before) format is downloaded and imported into SAP.

Regards,

Tomasz Gerke

gopalrawat
Explorer
0 Kudos

Hello Thomas,

Thanks for  the help.

checked with the same with our abaper. he did check the mentioned user Exit FEB00004.

While we  used the format " S " . The conversion of 3 characters is happening after user exit so our changes wont make any effect.

(Please find the screen shot attached)

Could please suggest another exit which is called after below mentioned screenshot.

Best Regards

Gopal Rawat

Former Member
0 Kudos

FEB00001 which is triggered after interpretation algorithm is executed (if it's used), BADi FIEB_CHANGE_BS_DATA (triggered before interpretation) and search strings. Please look at report RFEBBU10 which is the core of EBS interpretation.

Former Member
0 Kudos

Hi Gerke,

Could you please help me to understand whether the below format is structured or unstructured.

61:1402030203CR75946,00NNTCNONREF//AXISF14034083373

:86:3002 NEFT CR-UTIB0000024-M G ELECTRONICS STOCK EXCH

:61:1402030203CR220484,00NNTCNONREF//SAA75402949

:86:3002 NEFT CR-UBIN0557129-RAINBOW ELECTRICALS STOCK EXCH

:61:1402030203CR63498,00NNTCNONREF//ANDBN14034630267

:86:3002 NEFT CR-ANDB0000109-ANUSHA ELECTRICAL HO STOCK EXCH

:61:1402030203CR19684,00NNTCNONREF//BARBH14034295843

:86:3002 NEFT CR-BARB0KATNIX-SUVIDHA SALES CORPOR STOCK EXCH

:61:1402030203CR50000,00NNTCNONREF//CSBKN14034005174

:86:3002 NEFT CR-CSBK0000251-T P TILES AND SANITA STOCK EXCH

:61:1402030203CR5629,00NNTCNONREF//SFB21853543

:86:3002 NEFT CR-FDRL0001054-HHYS INFRAMART STOCK EXCH

:61:1402030203DR12650,26NMSCNONREF//007FT01140340025

:86:1022 FCY OUTWARD REMITTANCE BHAND-PUNE

:61:1402030203CR55000,00NNTCNONREF//P14020341370522

:86:3002 NEFT CR-CNRB0000594-SRI RAGHAVENDRA ELEC STOCK EXCH

:61:1402030203CR25000,00NNTCNONREF//ANDBN14034626797

:86:3002 NEFT CR-ANDB0000546-BARATAM SARWESWARARA STOCK EXCH

:61:1402030203CR148086,00NNTCNONREF//SAA22358669

:86:3002 NEFT CR-UCBA0000800-KEYA TRADERS. STOCK EXCH

:61:1402030203CR150000,00NNTCNONREF//SAA75354038

:86:3002 NEFT CR-UBIN0558150-MYSORE PIPE CENTRE STOCK EXCH

:61:1402030203CR200000,00NNTCNONREF//SBTR214034644094

:86:3002 NEFT CR-SBTR0000531-KINGS EECTRICALS STOCK EXCH

:61:1402030203DR90636,74NMSCNONREF//007FT01140340020

:86:1022 FCY OUTWARD REMITTANCE BHAND-PUNE

:61:1402030203CR100000,00NNTCNONREF//ANDBN14034625378

:86:3002 NEFT CR-ANDB0000895-MONARCH ELECTRONICS STOCK EXCH

:61:1402030203CR142434,00NNTCNONREF//UTBIN14034406846

:86:3002 NEFT CR-UTBI0KCHD17-S C PAUL STOCK EXCH

:61:1402030203CR133291,00NNTCNONREF//BARBH14034278974

:86:3002 NEFT CR-BARB0BLYRAJ-BALAJI ELECTRICALS STOCK EXCH

:61:1402030203CR121001,00NNTCNONREF//SM326650929

:86:3002 NEFT CR-ICIC0002577-SHRI DURGA FERTILIZE STOCK EXCH

:61:1402030203CR29189,00NNTCNONREF//SBTR214034644901

:86:3002 NEFT CR-SBTR0000675-MIHRAJ ELECTRICALS STOCK EXCH

:61:1402030203CR47000,00NNTCNONREF//SIBLN14034466819

:86:3002 NEFT CR-SIBL0000327-SUN ELECTRONICS STOCK EXCH

:61:1402030203CR24000,00NNTCNONREF//SFB21868345

:86:3002 NEFT CR-FDRL0001873-KAMALESH B STOCK EXCH

:61:1402030203CR100000,00NNTCNONREF//MAHBH14034665319

:86:3002 NEFT CR-MAHB0000346-BISINEER BASANNA CO STOCK EXCH

:61:1402030203CR3153,00NNTCNONREF//CIUBH14034389114

:86:3002 NEFT CR-CIUB0000265-GURRAM VENKATESWARLU STOCK EXCH

:61:1402030203CR129667,00NNTCNONREF//SAA9975547

:86:3002 NEFT CR-TMBL0000073-GANESH ELECTRICALS STOCK EXCH

:61:1402030203DR76583,00NCHKNONREF//000000967183

:86:6101 Chq Pd-Transfer-RAHDE AGNECIES EXT-NAVRANG

:61:1402030203DR83296,00NCHKNONREF//000000967390

:86:6101 Chq Pd-Transfer-RADHE AGNEICES EXT-NAVRANG

:61:1402030203CR341323,00NTRFNONREF//0000140203000025

:86:1431 CMS-FINCABLES-140203000025/MOD NETBANK

:61:1402030203CR86079,00NTRFNONREF

:86:2946 08252560000875-STP-Advance for FO Cable NETBANK

:61:1402030203DR15293,00NCTFNONREF//967005

:86:1521 CHQ PAID CMS MADU - SICAGEN INDIA LTD MADURAI

:61:1402030203DR187252,00NTRFNONREF//000000967291

:86:1006 FT --01702560007887-AQSA POLYMERS BHAND-PUNE

:61:1402040203CR59580,00NCOLNONREF/

Thanks in advance..!!

Former Member
0 Kudos

Hi, unstructured.

former_member194797
Active Contributor
0 Kudos

Hi,

In structured format, the 4th character after :86: is a separator, usualy quotation mark, and this separator must be followed by a 2 digit code like ?00 ?20 ?21, ... ?29 ... (as described in this document for example: http://www.lbbw.cz/srv/cps/content/files/en/our-clients/internet-banking/lbbw-structure-of-lbbw-busi... ).

?00, ?20, ?21 ... are special tags for delimiting predefined fields.

example:

:86:835?00xxxxxxxxx?20xxxxxxxxxxxxxxxxxxxxxxxxxxx?21xxxxxxxxxx?31xxx

In your case, you have no tag inside the :86: record; the format is obviously unstructured.

Former Member
0 Kudos

Hi,

Thanks for the quick reply..!!

I have done config by taking three character unique code from TAG 86 from 5 to 8 i.e 300, 610,143 as Transaction type & system is able to process the MT940. Earlier I created Transaction type with 4 character from TAG 61 i.e NNTC, NCHK & NTRF like that but system was not able to process file & it was giving an error as below. Could you help to understand why system behaving like that.

Account statement not updated Message no. FB773

:61:1402030203CR121001,00NNTCNONREF//SM326650929

:86:3002 NEFT CR-ICIC0002577-SHRI DURGA FERTILIZE STOCK EXCH

:61:1402030203DR83296,00NCHKNONREF//000000967390

:86:6101 Chq Pd-Transfer-RADHE AGNEICES EXT-NAVRANG

:61:1402030203CR341323,00NTRFNONREF//0000140203000025

:86:1431 CMS-FINCABLES-140203000025/MOD NETBANK

Thanks

Former Member
0 Kudos

Dear T Ger,

I’m trying to upload an Electronic bank statement format MT940 for a Mexican bank using FF.5.

I understood that if the line 86 has this form...

:86:902?00DEP CHEQUEBNM?20/EI/TRANSACTION?21

Then the MT940 is with field 86 structured.

In this way we created the entries into the T028G with three codes for the external transactions. Some samples 079, 364, 425, TRF…

With these setting I can process the file in SAP without process errors, but the movements in the bank statement in SAP are with wrongs.

When the file is processed the system did changing the operations (movements). Is like a concatenate some letters/numbers of line 61 and 86.

MT940

:20:9400515233021050

:25:001362XXYY

:28:15232

:60F:C150820MXN30362119,60

:61:1508200820CN0,00NCHK0000000000093131//4857175418

:86:902?00DEP CHEQUE BNM?20/EI/TRANSACTION?21    384,871.43

:61:1508200820CN485508,95NCHK0000000000107994//0458004409

:86:635?00DEPOSITO S.B.C.?20/EI/107994

:61:1508200820CN466470,37NTRF0000530130423256//0859072288

:86:364?00ORDEN DE ABONO?20/EI/0000093232  COMPRA DE INVENTARIO

View in FF.6


I don’t know which the problem is... Maybe you can give me any idea? Please!

Thanks!

Sandra Milena



former_member194797
Active Contributor
0 Kudos

Hi,

if you are working in MT940 86 structured format, the external transaction is a 3 digits code. In your case it is 906, as you see in your error message. If you have a 4 digits code, I think you have unstructured format.

joseluis_carbajo
Explorer
0 Kudos

Hi Gopal,

For possibilities to enhance the bank statement functionality, you
can refer to note 494777 point 10.

Exit FEB00004 is called at the import of SWIFT MT940 in program
RFEKA400.You can use this interface to convert bank-specific and/or
country specific changes to the SWIFT MT940 format into the form
recommended by SAP.


Hope this could be helpful for you.
Regards,

Jose