cancel
Showing results for 
Search instead for 
Did you mean: 

PO migration

Former Member
0 Kudos

Hello,

i`m using BAPI to create PORDCR103 and somehow I recive an text error when I want to post the idoc.

Text * ID * language * not found

Message no. TD600

Diagnosis

You want to read a text which does not exist in the data base (or update memory).

System Response

Reading could not be carried out.

Procedure

You need to create this text:

1. Initialization (module INIT_TEXT)

2. Save (module SAVE_TEXT)

Some ideas?

Regards,Nino

Accepted Solutions (0)

Answers (1)

Answers (1)

JL23
Active Contributor
0 Kudos

Post the error message as is, or is the language really a secret.

you probably have a 2 character language in your source file, but IDOC has only a 1 character field.

example. Language ZH is internal language 1 , if you move ZH into a one charcter long field, then just Z is left. but the Z language is not available in your system, hence the error message.

(see table T002, it has the ISO language and the internal language)

Former Member
0 Kudos

that is the message. There is no language ID in this error.

I know the mapping for language

LANGU = 'D'

LANGU_ISO = 'DE'

JL23
Active Contributor
0 Kudos

why is there no language?

you know that a longtext has as key the text object, text id, text name and language.

the language from PO header structure does not automatically default to the language for long text structure

Former Member
0 Kudos

- mapping contains language, the error massage does't contain the lang ID

- i dont use any long text on header or any position text for the migration

- I also deactivated all text setting (automatic text) for the migration

JL23
Active Contributor
0 Kudos

have you displayed your IDOC in detail? does it have the language?

if not, then it must be an error in the program you used to create it, is it an ABAP or LSMW?

Former Member
0 Kudos

Yes it has an language and I`m using LSMW with BAPI

JL23
Active Contributor
0 Kudos

the original error message you posted was:

Text * ID * language * not found

so this message clearly talkes about some long text.

but you are saying now: - i dont use any long text on header or any position text for the migration

please see your IDOC in WE02 and tell me which segments it has.

Former Member
0 Kudos

Thats whay I cant understand this error message

The segments of the idoc

E1BPMEPOHEADER

E1BPMEPOHEADERX

E1BPMEPOITEM

E1BPMEPOITEM1

E1BPMEPOITEMX

In those segments there are no text fields with text ID

JL23
Active Contributor
0 Kudos

can you create a PO with that vendor and language manually?

or do you get the same error?

For message processing you can assign standard text e.g. to the purchasing organisation.

of course those texts have to be there in the language of the PO.