Regarding IDOCs

[sreeramkumar_madisetty]

Hello Friends

Sorry for repeating the question.

But in a hurry to get the answer bcoz it's urgent i am doing this.

This is my requirement & Problem description.

Please kindly go thru it and help me.

I am running the report ZRFFOUSC (Combination of standard print programs RFFOUS_C and RFFOEDI ). This program is creating the IDOC as follows.

<b>Fldname Fld Cont</b>

FIIQUALI BB

FIIBKENN 053000219

FIIBKCDE 003

FIIBKNAM WACHOVIA BANK NA

FIIBKORT CHARLOTTE

FIIBLAND US

FIIKONTO 1000000132919

FIIBKONT 1

FIIBRANCH VICKIE MORRIS 336-732-5560

Now the problem is in Acceptance it's working fine while in production,I am getting

<b>Fldname Fld Cont</b>

FIIQUALI BB

FIIBKENN 053000219

FIIBKCDE 003

junkdata junkdata

junkdata junkdata

FIIBKNAM WACHOVIA BANK NA

FIIBKORT CHARLOTTE

FIIBLAND US

FIIKONTO 1000000132919

FIIBKONT 1

FIIBRANCH VICKIE MORRIS 336-732-5560

As I am very new to IDOCs i am not able to find why this junk data is comming in production system only.

Please help me how i can findout the problem and rectify the same.

<b>Atleast let me know the debugging procedure where i have to concentrate mainly.</b>

<b>Points are guaranteed for helpful answers.</b>

Regards,

Sreeram

[sreeramkumar_madisetty]

I'm not familiar with any of these programs, but to debug you'll need to add a break point in your program. If this does not work, there is one trick to debug hard to reach places. Put an indefinite loop in the place you need to debug. Start the program, you should see it running in SM50, from there you can jump into debugger.

Please keep in mind that this should be used only if there is no other way and proceed with caution!

[Jelena_Perfiljeva]

I'm not familiar with any of these programs, but to debug you'll need to add a break point in your program. If this does not work, there is one trick to debug hard to reach places. Put an indefinite loop in the place you need to debug. Start the program, you should see it running in SM50, from there you can jump into debugger.

Please keep in mind that this should be used only if there is no other way and proceed with caution!

[Former Member]

Hi,

What is this junk data you are talking about.

Are you using IDOC PEXR2002?

Are you talking about segment E1IDB02 (IDOC header - extended bank details )?

If you look at the structure of segment E1IDB02, the fields are like this.

1.	FIIQUALI
2.	FIIBKENN
3.	FIIBKCDE
4.	FIIBKUKN
5.	FIIBKUCD
6.	FIIBKNAM
7.	FIIBKORT
8.	FIIBLAND
9.	FIIKONTO
10.	FIIKNAME
11.	FIIKNAM2
12.	FIIKWAER
13.	CTAFUNKT
14.	CTABNAME
15.	COMNUMM1
16.	COMNART1
17.	COMNUMM2
18.	COMNART2
19.	COMNUMM3
20.	COMNART3
21.	COMNUMM4
22.	COMNART4
23.	COMNUMM5
24.	COMNART5
25.	FIIBKONT
26.	FIIXPGRO
27.	FIIBRANCH

The field no. 3 is <b>FIIBKCDE</b> while field no 6 is <b>FIIBKNAM</b>. You are saying that you are getting junk data between these two fields in production.

But if you see closely there two more fields between these two fields.

- field 4 <b>FIIBKUKN</b>

- field 5 <b>FIIBKUCD</b>.

you must be getting these two populated in production because there might be a data in production which is not in your development client. These are not junk data. SAP populate these data if it exist. I am suspecting that you are considering these two fields as junk fields. BUT THEY ARE NOT JUNK DATA.

Let me know if you are not talking about the two fields i have mentioned above. If they are not the two fields then there must be some custom code involve here because SAP does not populate any data without any meaning.

Do let me know if you are using the same IDOC i have mentioned above or not? If not than give me the IDOC name and segment you are having issue with, i can help you.

Let me know if you have any questions.

Regards,

RS

[sreeramkumar_madisetty]

It's answered