short dump (UC_OBJECTS_NOT_CONVERTIABLE)

[Former Member]

Hi Frineds,

when user executes planning folder in UPSPL tranaction in the Quality system it is working fine without any errors.

But when he exucte the same planning folder in UPSPL transaction in the Dev system , the generated ABAP program going to short dump.

Error message: (UC_OBJECTS_NOT_CONVERTIABLE)

Short text:

Data objects in a Unicode program ae not convertible

Error analysis:

The statement "Move src To dst"

requires the operands "dst" and "src" to the convertible.

does any body had the same problem.

Please give me some suggestions why it is happening, it is running in the quality system but in the developement it is giving error.

what could be the problem?

does it related to Unicode system error or any datatypes.

It shows the errot at the following line in the ABAP program.

Loop at i_t_facttable into l_s_facttable.

It is very urgent for me.

Please help me how to solve this issue.

Give me some inputs where i need to check this tyep error.

It would be grat help for me.

will assign the points.

Thanks

BPS

[Former Member]

Hi,

As this is the standard SAP transaction going for dump,so check in the OSS you may get solution for this.

Regards,

Atish

[Former Member]

Yes, if this is a standard SAP program you should check OSS first.

If the line "Loop at i_t_facttable into l_s_facttable." is giving the error, check that l_s_facttable has the same structure as i_t_facttable. One reason it may happen is DEV but not QAS would be that you may have Unicode checking in in development but not elsewhere.

[Former Member]

Hi,

Thanks for ur reply. I already checked the OSS note.

In the OSS note i couldn't find any relevant notes.

Right now we are in SAP BW 3.5 version.

I found one one SAP OSS note for BW 3.0B version(SAP Note: 587043).

we already applied earlier this note.

If anybody had this problem earlier. Please let me know what is the relevant SAP Note.

How to test whether Unicode is applied or not for Dev, QA systems.

Please give me some suggestions how to test the Unicode checks,

Thanks

BPS

[Former Member]

> It shows the errot at the following line in the ABAP

> program.

>

> Loop at i_t_facttable into l_s_facttable.

It woudl be more helpful to have the types (structure) of the table and work field than just their names.

it is very probable that a data element in the table i_t_facttable is defined differently from a data element in the structure l_s_facttable, but without the detailed information on the structures, it is hard to tell.

In particular, if there are alignment problems where the lengths of fields are different, whether due to double-byte vs. single byte, etc, or where numeric fields are being mapped incorrectly, you will get this problem.

If you provide the structure layouts, someone should be able to see exact location of the problem.

Good luck

Brian

[Former Member]

Hi Brian,

Thanks for ur reply. It is SAP generated program. But the same trasaction is working in the Quality system. But it is not working in the Dev system.

How to find out the Generated program in the Quality system.

In the developement system i find out the program name in the St22.

Can anybody suggested me how to find the SAP generated ABAP program for UPSPL tranasction. If i get the QA program i can see both the programs.

Please help me in this regards.

Thanks guys,

thanks

BPS

[Former Member]

UPB_PM_CUST_START is the program on my system.

You can always find the program for a transaction by displaying the transaction using SE84, Information System.

Use SE84, expand "Other objects", double click on "Transactions". Type your transaction code in the selection box and execute.

You will get a list like this:

  Transaction Code     Short text                                                                                
UPSPL                Execute Generic Planning Folder  

Select to display the transaction when it comes up. It will show you the program name.

Now that you have the program name, you should be able to navigate this as usual and drill down to find any detailed info on it that you need.

Good luck

Brian

[Former Member]

thanks brian. it is very helpful for me.

Here iam attaching my generated program. Can you look into this one. Please suggest me if any changes required.

----

---

• SAP Business Information Warehouse

*

• This report has been generated from a template.

*

• !!! DO NOT CHANGE !!!

*

• Programname : GP43FOKDF6HBML0GQNU7VSY8JC2

• Template : RSAPOTMPWRITEIC (Version BW 3.0)

• Generated at : 01/23/2007 11:04:41

• Generated by : SPATRO

----

---

report GP43FOKDF6HBML0GQNU7VSY8JC2 .

type-pools: rs, rsarr, rssm, rsau, rsdrc, rsdw, rsd, abap.

include rsagui.

• types for RFC facttable format

data: g_s_rfcinput type rsdri_s_rfcdata.

• types for facttable

types: gt_s_facttable type /BIC/VZTBUD1022.

types: gt_t_facttable type standard table of gt_s_facttable

with default key initial size 0.

• types for facttable extended by boolean flags for each keyfigure

• (requirement of the FS program 'GP43FOKCS4WFTGGL4BCPOS42N6Q')

types: begin of gt_s_cube.

include structure /BIC/VZTBUD102T.

types:

• fZAFT_DIFF0001 type rs_bool, "BW 3.0B SP15

fZAFT_DIFF type rs_bool,

• fZAFT_HLTH0002 type rs_bool, "BW 3.0B SP15

fZAFT_HLTH type rs_bool,

• fZAFT_MEDI0003 type rs_bool, "BW 3.0B SP15

fZAFT_MEDI type rs_bool,

• fZAFT_PARS0004 type rs_bool, "BW 3.0B SP15

fZAFT_PARS type rs_bool,

• fZAFT_PERS0005 type rs_bool, "BW 3.0B SP15

fZAFT_PERS type rs_bool,

• fZAFT_SAL0006 type rs_bool, "BW 3.0B SP15

fZAFT_SAL type rs_bool,

• fZAFT_SS0007 type rs_bool, "BW 3.0B SP15

fZAFT_SS type rs_bool,

• fZAFT_STRS0008 type rs_bool, "BW 3.0B SP15

fZAFT_STRS type rs_bool,

• fZAFT_TBEN0009 type rs_bool, "BW 3.0B SP15

fZAFT_TBEN type rs_bool,

• fZAFT_UNEM0010 type rs_bool, "BW 3.0B SP15

fZAFT_UNEM type rs_bool,

• fZAFT_WCOM0011 type rs_bool, "BW 3.0B SP15

fZAFT_WCOM type rs_bool,

• fZAMT_DIFF0012 type rs_bool, "BW 3.0B SP15

fZAMT_DIFF type rs_bool,

• fZAMT_FRTO0013 type rs_bool, "BW 3.0B SP15

fZAMT_FRTO type rs_bool,

• fZAMT_HLTH0014 type rs_bool, "BW 3.0B SP15

fZAMT_HLTH type rs_bool,

• fZAMT_MEDI0015 type rs_bool, "BW 3.0B SP15

fZAMT_MEDI type rs_bool,

• fZAMT_PARS0016 type rs_bool, "BW 3.0B SP15

fZAMT_PARS type rs_bool,

• fZAMT_PERS0017 type rs_bool, "BW 3.0B SP15

fZAMT_PERS type rs_bool,

• fZAMT_SAL0018 type rs_bool, "BW 3.0B SP15

fZAMT_SAL type rs_bool,

• fZAMT_SS0019 type rs_bool, "BW 3.0B SP15

fZAMT_SS type rs_bool,

• fZAMT_STRS0020 type rs_bool, "BW 3.0B SP15

fZAMT_STRS type rs_bool,

• fZAMT_TBEN0021 type rs_bool, "BW 3.0B SP15

fZAMT_TBEN type rs_bool,

• fZAMT_TSAL0022 type rs_bool, "BW 3.0B SP15

fZAMT_TSAL type rs_bool,

• fZAMT_UNEM0023 type rs_bool, "BW 3.0B SP15

fZAMT_UNEM type rs_bool,

• fZAMT_WCOM0024 type rs_bool, "BW 3.0B SP15

fZAMT_WCOM type rs_bool,

• fZDYSPWK0025 type rs_bool, "BW 3.0B SP15

fZDYSPWK type rs_bool,

• fZFTEPCT0026 type rs_bool, "BW 3.0B SP15

fZFTEPCT type rs_bool,

• fZFUNDPCT0027 type rs_bool, "BW 3.0B SP15

fZFUNDPCT type rs_bool,

• fZHRSPDY0028 type rs_bool, "BW 3.0B SP15

fZHRSPDY type rs_bool,

• fZHRSPMO0029 type rs_bool, "BW 3.0B SP15

fZHRSPMO type rs_bool,

• fZPSTEDT0030 type rs_bool, "BW 3.0B SP15

fZPSTEDT type rs_bool,

• fZPSTSDT0031 type rs_bool, "BW 3.0B SP15

fZPSTSDT type rs_bool,

recno type RSARECORD,

end of gt_s_cube.

types: gt_t_cube type standard table of gt_s_cube

with default key initial size 100.

• variables that are required only as parameters for perform-call

data: g_s_minfo type rssm_s_minfo,

g_datap type rsarr_s_receive_header3-datapakid,

g_idocnum type rsarr_idoc_docnum,

g_t_idocstate type rsarr_t_idocstate,

g_subrc like sy-subrc.

----

---

• FORM APO_WRITEIC *

----

---

• main form routine that can be called from outside to

• write data into the infocube ZTBUD102

----

---

form apo_writeic

using i_infocube type rsinfocube

i_requid type rsrequnr

i_t_input type standard table

i_curr_conversion type rs_bool

i_called_by_rfc type rs_bool

changing e_subrc.

data : l_t_facttable type gt_t_facttable,

l_t_cube type gt_t_cube.

• progress indicator: data write

g_text_gui = 'Data is written into the infocube ...'(001).

gui_message.

• set REQUID

g_s_minfo-requnr = i_requid.

• conversions

if i_called_by_rfc = rs_c_true.

perform rfcinput_to_facttable

using i_t_input

changing l_t_facttable.

perform facttable_to_cube

using l_t_facttable

changing l_t_cube.

else.

perform facttable_to_cube

using i_t_input

changing l_t_cube.

endif.

perform set_parameters.

• write data

perform writeic

using l_t_cube.

e_subrc = g_subrc.

endform. "apo_writeic

----

---

• FORM RFCINPUT_TO_FACTTABLE *

----

---

• moves data from the RFC input table (in a standard format)

• to an internal table that matches the structure of the

• infocube ZTBUD102.

----

---

• --> I_T_RFCINPUT *

----

---

form rfcinput_to_facttable

using i_t_rfcinput type rsdri_t_rfcdata

changing e_t_facttable type gt_t_facttable.

call function 'RSDRI_DATA_UNWRAP'

EXPORTING

i_t_rfcdata = i_t_rfcinput

CHANGING

c_t_data = e_t_facttable.

endform. "rfcinput_to_facttable

----

---

• FORM FACTTABLE_TO_CUBE *

----

---

• copy t_facttable to l_t_cube

----

---

form facttable_to_cube

using i_t_facttable type standard table "gt_t_facttable

changing e_t_cube type gt_t_cube.

data: l_s_facttable type gt_s_facttable,

l_s_cube type gt_s_cube.

clear e_t_cube.

loop at i_t_facttable into l_s_facttable.

clear l_s_cube.

move l_s_facttable-0CHNGID

to l_s_cube-CHNGID.

move l_s_facttable-0RECORDTP

to l_s_cube-RECORDTP.

move l_s_facttable-0REQUID

to l_s_cube-REQUID.

move l_s_facttable-0FISCPER

to l_s_cube-FISCPER.

move l_s_facttable-0FISCVARNT

to l_s_cube-FISCVARNT.

move l_s_facttable-0FISCYEAR

to l_s_cube-FISCYEAR.

move l_s_facttable-0CURRENCY

to l_s_cube-CURRENCY.

move l_s_facttable-0FM_AREA

to l_s_cube-FM_AREA.

move l_s_facttable-0FUND

to l_s_cube-FUND.

move l_s_facttable-ZSACSFUND

to l_s_cube-/BIC/ZSACSFUND.

move l_s_facttable-ZSACSRSRC

to l_s_cube-/BIC/ZSACSRSRC.

move l_s_facttable-ZSACSGOAL

to l_s_cube-/BIC/ZSACSGOAL.

move l_s_facttable-ZSACSFUNC

to l_s_cube-/BIC/ZSACSFUNC.

move l_s_facttable-ZLAUSDPGM

to l_s_cube-/BIC/ZLAUSDPGM.

move l_s_facttable-0FUNDS_CTR

to l_s_cube-FUNDS_CTR.

move l_s_facttable-0FUNC_AREA

to l_s_cube-FUNC_AREA.

move l_s_facttable-0CMMT_ITEM

to l_s_cube-CMMT_ITEM.

move l_s_facttable-0PU_MEASURE

to l_s_cube-PU_MEASURE.

move l_s_facttable-0GRANT_NBR

to l_s_cube-GRANT_NBR.

move l_s_facttable-ZFMBDDTYP

to l_s_cube-/BIC/ZFMBDDTYP.

move l_s_facttable-ZFMBDTYP

to l_s_cube-/BIC/ZFMBDTYP.

move l_s_facttable-0HRPOSITION

to l_s_cube-HRPOSITION.

move l_s_facttable-0JOB

to l_s_cube-JOB.

move l_s_facttable-ZPSTSTAT

to l_s_cube-/BIC/ZPSTSTAT.

move l_s_facttable-0PERS_AREA

to l_s_cube-PERS_AREA.

move l_s_facttable-0PERS_SAREA

to l_s_cube-PERS_SAREA.

move l_s_facttable-0COUNTRY_ID

to l_s_cube-COUNTRY_ID.

move l_s_facttable-0ESGFORCAP

to l_s_cube-ESGFORCAP.

move l_s_facttable-0PAYSCALEAR

to l_s_cube-PAYSCALEAR.

move l_s_facttable-0PAYSCALEGR

to l_s_cube-PAYSCALEGR.

move l_s_facttable-0PAYSCALELV

to l_s_cube-PAYSCALELV.

move l_s_facttable-0PAYSCALETY

to l_s_cube-PAYSCALETY.

move l_s_facttable-ZPST_IND

to l_s_cube-/BIC/ZPST_IND.

move l_s_facttable-0VERSION

to l_s_cube-VERSION.

move l_s_facttable-ZUSERID

to l_s_cube-/BIC/ZUSERID.

move l_s_facttable-ZTIME

to l_s_cube-/BIC/ZTIME.

move l_s_facttable-ZBUDLNTYP

to l_s_cube-/BIC/ZBUDLNTYP.

move l_s_facttable-ZDATE

to l_s_cube-/BIC/ZDATE.

move l_s_facttable-ZBAPVSTAT

to l_s_cube-/BIC/ZBAPVSTAT.

move l_s_facttable-ZCOBUDITM

to l_s_cube-/BIC/ZCOBUDITM.

move l_s_facttable-ZBUDITEM

to l_s_cube-/BIC/ZBUDITEM.

move l_s_facttable-ZPSTTEMP

to l_s_cube-/BIC/ZPSTTEMP.

move l_s_facttable-ZCOMMENT

to l_s_cube-/BIC/ZCOMMENT.

move l_s_facttable-ZNORM_IND

to l_s_cube-/BIC/ZNORM_IND.

move l_s_facttable-ZSUBJECT1

to l_s_cube-/BIC/ZSUBJECT1.

move l_s_facttable-ZSUBJECT2

to l_s_cube-/BIC/ZSUBJECT2.

move l_s_facttable-ZSUBJECT3

to l_s_cube-/BIC/ZSUBJECT3.

move l_s_facttable-ZGUID

to l_s_cube-/BIC/ZGUID.

move l_s_facttable-ZPSTSDT

to l_s_cube-/BIC/ZPSTSDT.

move l_s_facttable-ZPSTEDT

to l_s_cube-/BIC/ZPSTEDT.

move l_s_facttable-ZHRSPDY

to l_s_cube-/BIC/ZHRSPDY.

move l_s_facttable-ZDYSPWK

to l_s_cube-/BIC/ZDYSPWK.

move l_s_facttable-ZFTEPCT

to l_s_cube-/BIC/ZFTEPCT.

move l_s_facttable-ZFUNDPCT

to l_s_cube-/BIC/ZFUNDPCT.

move l_s_facttable-ZAMT_DIFF

to l_s_cube-/BIC/ZAMT_DIFF.

move l_s_facttable-ZAMT_FRTO

to l_s_cube-/BIC/ZAMT_FRTO.

move l_s_facttable-ZAMT_HLTH

to l_s_cube-/BIC/ZAMT_HLTH.

move l_s_facttable-ZAMT_MEDI

to l_s_cube-/BIC/ZAMT_MEDI.

move l_s_facttable-ZAMT_PARS

to l_s_cube-/BIC/ZAMT_PARS.

move l_s_facttable-ZAMT_PERS

to l_s_cube-/BIC/ZAMT_PERS.

move l_s_facttable-ZAMT_SAL

to l_s_cube-/BIC/ZAMT_SAL.

move l_s_facttable-ZAMT_SS

to l_s_cube-/BIC/ZAMT_SS.

move l_s_facttable-ZAMT_STRS

to l_s_cube-/BIC/ZAMT_STRS.

move l_s_facttable-ZAMT_TBEN

to l_s_cube-/BIC/ZAMT_TBEN.

move l_s_facttable-ZAMT_TSAL

to l_s_cube-/BIC/ZAMT_TSAL.

move l_s_facttable-ZAMT_UNEM

to l_s_cube-/BIC/ZAMT_UNEM.

move l_s_facttable-ZAMT_WCOM

to l_s_cube-/BIC/ZAMT_WCOM.

move l_s_facttable-ZAFT_DIFF

to l_s_cube-/BIC/ZAFT_DIFF.

move l_s_facttable-ZAFT_HLTH

to l_s_cube-/BIC/ZAFT_HLTH.

move l_s_facttable-ZAFT_MEDI

to l_s_cube-/BIC/ZAFT_MEDI.

move l_s_facttable-ZAFT_PARS

to l_s_cube-/BIC/ZAFT_PARS.

move l_s_facttable-ZAFT_PERS

to l_s_cube-/BIC/ZAFT_PERS.

move l_s_facttable-ZAFT_SAL

to l_s_cube-/BIC/ZAFT_SAL.

move l_s_facttable-ZAFT_SS

to l_s_cube-/BIC/ZAFT_SS.

move l_s_facttable-ZAFT_STRS

to l_s_cube-/BIC/ZAFT_STRS.

move l_s_facttable-ZAFT_UNEM

to l_s_cube-/BIC/ZAFT_UNEM.

move l_s_facttable-ZAFT_WCOM

to l_s_cube-/BIC/ZAFT_WCOM.

move l_s_facttable-ZHRSPMO

to l_s_cube-/BIC/ZHRSPMO.

move l_s_facttable-ZAFT_TBEN

to l_s_cube-/BIC/ZAFT_TBEN.

append l_s_cube to e_t_cube.

endloop.

endform. "facttable_to_cube

----

---

• FORM SET_PARAMETERS *

----

---

• set parameters for the 'perform writeic(...)' call

----

---

form set_parameters.

• set REQUNR = REQUID (of the last record inserted into l_t_cube)

• L_S_MINFO-REQUNR = L_S_CUBE-REQUID.

• write data even if there is no master data

g_s_minfo-bookmode = rsau_c_idoc_bk-auto_sid.

• set the following ID as a default

g_datap = '000001'.

endform. "set_parameters

----

---

• FORM WRITEIC *

----

---

• calls the writeic form in gp43FOKCS4WFTGGL4BCPOS42N6Q

• that writes the data into the facttable of the infocube

• ZTBUD102

----

---

form writeic

using i_t_cube type gt_t_cube.

data: l_t_chavlerr type rsdw_t_chavlerr.

• write into infocube

perform writeic(gp43FOKCS4WFTGGL4BCPOS42N6Q)

using i_t_cube

g_s_minfo

g_datap

• g_idocnum

changing l_t_chavlerr

g_t_idocstate

g_subrc.

if g_subrc = 42.

• --- rollback

ROLLBACK WORK.

else.

• --- commit

call function 'RSDU_DB_COMMIT'

EXCEPTIONS

others = 1.

if sy-subrc <> 0.

raise others.

endif.

endif.

endform. "writeic

.. The following subroutine is for internal (FuGr RSSG) use only! ..

FORM RSSGPROGRAM_LOADCHECK

CHANGING E_S_PDIR TYPE RSSGTPDIR

E_FOUND TYPE FLAG.

CONSTANTS:

BEGIN OF RSSGC_PCLA,

PROGCLASS TYPE RSSGTPCLA-PROGCLASS

VALUE 'RSAPOWRITEIC',

CLIDEP TYPE RSSGTPCLA-CLIDEP

VALUE ' ',

GENFLAG TYPE RSSGTPCLA-GENFLAG

VALUE 'X',

SUBC TYPE RSSGTPCLA-SUBC

VALUE '1',

TEMPLATE TYPE RSSGTPCLA-TEMPLATE

VALUE 'RSAPOTMPWRITEIC',

END OF RSSGC_PCLA,

BEGIN OF RSSGC_PDIR,

UNI_IDC25 TYPE RSSGTPDIR-UNI_IDC25

VALUE '43FOKDF6HBML0GQNU7VSY8JC2',

CLIENT TYPE RSSGTPDIR-CLIENT

VALUE ' ',

PROGCLASS TYPE RSSGTPDIR-PROGCLASS

VALUE 'RSAPOWRITEIC',

PROGNAME TYPE RSSGTPDIR-PROGNAME

VALUE 'GP43FOKDF6HBML0GQNU7VSY8JC2',

CREUSER TYPE RSSGTPDIR-CREUSER

VALUE 'RDELF',

CRETSTMP TYPE RSSGTPDIR-CRETSTMP

VALUE 20061017224109,

GENUSER TYPE RSSGTPDIR-GENUSER

VALUE 'SPATRO',

GENTSTMP TYPE RSSGTPDIR-GENTSTMP

VALUE 20070123190533,

GENRELEASE TYPE RSSGTPDIR-GENRELEASE

VALUE '640',

GENSTATUS TYPE RSSGTPDIR-GENSTATUS

VALUE '00',

UPDUSERTPL TYPE RSSGTPDIR-UPDUSERTPL

VALUE 'SAP',

UPDDATETPL TYPE RSSGTPDIR-UPDDATETPL

VALUE '20040812',

UPDTIMETPL TYPE RSSGTPDIR-UPDTIMETPL

VALUE '160952',

SUBC TYPE RSSGTPDIR-SUBC

VALUE ' ',

END OF RSSGC_PDIR.

MOVE-CORRESPONDING RSSGC_PDIR TO E_S_PDIR.

E_FOUND = 'X'.

ENDFORM.

[Former Member]

Hi Brian,

I entered trnaasction code and short text in SE84 trnaaction as you said.

After that i click on execute button, but i dont see any displayed information. How to find out the Generated abap program name for UPSPL tranaction.

Thanks

BPS

[Former Member]

Just enter transaction code in the selection box. This is unique. Or just enter a generic, like UPS*

If you mistype the short text, you might accidentally exclude the transaction code from the list. Don't enter the short text.

Brian

[Former Member]

I think there may be a bug in the generated code.

form facttable_to_cube
using i_t_facttable type standard table "gt_t_facttable
changing e_t_cube type gt_t_cube.

The second like of the quoted portion should read

using i_t_facttable type standard table of gt_s_facttable

This will ensure that casting occurs properly.

There may be a bug in the program generation process. If the change works, you should report this bug to SAP.

Brian

[Former Member]

Hi Brain,

Thanks for ur quick response. Let me see ur changes. I will change the program and i will test it.

This is SAP standard program so how to change the program, i think if we execute the trnasaction UPSPL each time we will get diddfrent ABAP program.

How to modify this one.

Please suggest me.

Thank you very much. I appreicated ur quick response.

I assigned the full points.

Thanks

sg

[Former Member]

You need to change the generated program GP43FOKDF6HBML0GQNU7VSY8JC2 that you posted. It is normally not recommended to change generated programs, but you have to fix your problem. If you find that the change works, report the problem to SAP, and they can generate a note for the problem.

The change that I recommend is in my previous response, and I have quoted it below in a post script. Also, not that my recommendation is based on the possibility that the parameter is not be typed properly currently, which is causing conversion problems.

If you change it, and the program is in the SAP namespace, you will have to use the modification assistant. You may need to get an SSCR key in this case.

It might be easier if you can make a copy of the program, make the change to the copy and test it.

WIth regard to the question of whether it generates a new program each time, I do not think so.

I don't think it generates a new program each time, since the generated program source that you posted says that it was generated on 01/23/2007. If a new program was generated each time, wouldn't it have today's date?

The important thing is to see if it solves the problem. If it does, then you have to report it to SAP so they can fix the program generator or program template, since others may end up with the same problem.

Good luck

Brian

PS

form facttable_to_cube
using i_t_facttable type standard table "gt_t_facttable
changing e_t_cube type gt_t_cube.

The second like of the quoted portion should read

using i_t_facttable type standard table of gt_s_facttable

[Former Member]

thanks a lot Brain.

I hope ur suggestions will work.

how to proceed right now?

Do i need to change the originoal program according to ur suggestions or should i write a note to SAP.

Right now my user wants to run the UPSPL trnaction Dev. what i have to do?

Thanks

BPS

[Former Member]

thanks brian.

I hope my problem will resolve.

i asigned the points.

I qppreicate ur quick resposnse

[Former Member]

Have you compared the sources for the generated program from the Quality system and Dev? Are they the same at this time? One of them may have been regenerated and they may be out of sync.

Is it possible for you to regenerate the program to see if this resolves it?

I wrote a quick test program to try to duplicate the conditions in the generated program to check if the general problem that I thought I saw was real, but I wasn't able to reproduce the error, so I may have been going under a false assumption. My code suggestion may not work.

There may be something else going on that I can't see.

Compare the programs and object attributes.

Is the source in both environments the same?

Is unicode checking on in both environments and for both programs?

If you debug the processes in each environment, how do the table and structure layouts compare?

Is the type /BIC/VZTBUD1022 that is referenced in the generated program the same in both environments?

good luck

Brian

[Former Member]

> thanks brian.

> I hope my problem will resolve.

> i asigned the points.

> I qppreicate ur quick resposnse

Did you solve your problem?

What was the ultimate resolution?

I would like to know if the suggestions helped.

Brian