EMIGALL for long text

[Former Member]

Hello'

I am looking for a way to transfer long text for object device location through Emigall.

Someone knows how to do it?

Thanks,

Ben

[william_eastman]

Ben:

You should be able to add one of the fields (there are several longtext fields available) form EGPLD to the input structure within your own migration company. Then you could map it to the input field in your file. You can also try object NOTE_DLC to import texts for Devloc.

regards,

bill.

[Former Member]

Hello Bill,

I don't find any long text in structure EGPLD.

You have a field name?

Thanks in advance,

Ben

[friedrich_keller]

Hello Ben,

Please use the field EGPLD-PLTXT to migrate a description of a device location. This field is not configured to be used by default. You need to change the field rule first:

- mark the DEVLOC migration object with a double-click

- mark the EGPLD structure with a double-click

- menu Field -> Display List -> All to display all field of EGPLD structure

- double-click on field PLTXT and change the field rule to 'transfer' (don't forget to mark the 'Generate' field.

Kind regards,

Fritz

[Former Member]

Thanks for your answer,

I manage to transfer fonctionnal location description, my problem is in transfering functlocation long text.

Knows how to do?

Ben

[Former Member]

Hi Ben,

I have the same issue with the long text issue for the Device location, have you found out the way to do it, if you have can you share it with me,

thanks in advance,

Robert.

[friedrich_keller]

..

[friedrich_keller]

Ben,

I think you are referring to the screen field EENO_DYNP-ZEILE (it's the last line at the bottom of the screen).

There you can add multiple text lines for the technical objects connection object and device location.

There is no migration object available to migrate this information. But you can easily create an own

BAPI migration object using an own project specific function module (see suggestion below).

You will need to define the field rules as follows:

Field / Field rule

x_head-tdobject = 'IFLOT' fixed value

x_head-tdname = <ID of technical object> via KSM (e.g. DEVLOC)

x_head-tdid = 'LTXT' fixed value

x_head-tdspras = sy-langu fixed value

x_head-tdform = 'SYSTEM' fixed value

x_head-tdlinesize = 132 fixed value

xt_line_tab-tdformat = '*' fixed value

Finally you need to adjust the RETURN-FIELD of the newly created BAPI migration object to AUTO-X_HEAD-TDNAME

and you are ready to migrate the long texts. Please let me know whether this solution works for you.

Kind regards,

Fritz

PS: In you can find out how to create a BAPI migration object.

FUNCTION zzmig_save_long_text.

*"----

---

""Interface local:

*" IMPORTING

*" REFERENCE(X_HEAD) TYPE THEAD

*" EXPORTING

*" REFERENCE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2

*" TABLES

*" XT_LINE_TAB STRUCTURE TLINE

*"----

---

• save long text of an technical object

CLEAR return.

CALL FUNCTION 'SAVE_TEXT'

EXPORTING

client = sy-mandt

header = x_head

savemode_direct = 'X'

TABLES

lines = xt_line_tab

EXCEPTIONS

id = 1

language = 2

name = 3

object = 4

OTHERS = 5.

IF sy-subrc <> 0.

• return error message

CALL FUNCTION 'BALW_BAPIRETURN_GET2'

EXPORTING

type = sy-msgty

cl = sy-msgid

number = sy-msgno

par1 = sy-msgv1

par2 = sy-msgv2

par3 = sy-msgv3

par4 = sy-msgv4

IMPORTING

return = return.

ENDIF.

ENDFUNCTION.

[Former Member]

Fritz,

This solution does give you long text on Devie Location, but when I see into it's corresponding Function location it comes as blank.

Kindly Help.