migration of 3.x DataSources in Nw2004s - where is soursystem gone ?

[gerald_sauerwein]

Hello,

I'm wondering from what the 0SOURSYSTEM can be filled using a migrated 3.x datasource. Such a datasource does not offer a source system id (and you can not add an additional line to that).A comm-structure which served such an information in a former release is not used anymore.

But in case you create a transformation, you have to create a rule for 0SOURSYSTEM, otherwise it will be left blank.

The NW2004s developer guide reads that this information will be added automatically while transferring data. Does this mean I have to delete all entries for 0SOURSYSTEM in my ruleset?

Thanks,

[Former Member · Accepted solution]

Hello Gerald,

first of all, sorry for my terrible english

your right. You have to create a rule for 0SOURSYSTEM, but in NW2004s the 0SOURSYSTEM and 0LOGSYS will be added automatically, if you use the ruletyp CONSTANT and left the value on INITIAL.

HINT: To see what happend, when using a CONSTANT for mapping 0SOURSYSTEM and 0LOGSYS look under 'EXTRA' -> 'DISPLAY GENERATED PROGRAM'. Search 0SOURSYSTEM and you find Coding like below

Hope to help

best regards

Thomas

-

---

TYPES:

BEGIN OF tyG_1,

InfoObject: 0SOURSYSTEM Quellsystem ID.

SOURSYSTEM TYPE RSSOURSYSID,

G1-SOURSYSTEM = R4-_1_1.

PERFORM convert_0SOURSYSTEM

USING

l_recno_SC_1

'xxxxxxxxxx' <<---logical Systemname

'0SOURSYSTEM'

CHANGING

G1-SOURSYSTEM

iro_subrc.