вторник, 24 марта 2015 г.

Import/Export to memory

data:
      gl_flag           type c length 1.


    import gl_flag to gl_flag from memory id 'flag_reserve'.
    if gl_flag is initial.

      gl_flag = 'X'.
      export gl_flag from gl_flag to memory id 'flag_reserve'.
    endif.

вторник, 17 марта 2015 г.

Дамп при попытке зайти в инфо-пакет. MESSAGE_TYPE_X SAPLRSSM

Оказалось, два раза была запущена инициализация.

При входе в инфо-пакет - дамп:


Помогло удалить левые записи инициализации в таблицах ROOSPRMSC and ROOSPRMSF на стороне исходной системы:


OSS is your friend... search for MESSAGE_TYPE_X and RSSM_OLTPSOURCE_SELECTIONS gives you note 852443:

Symptom

If a MESSAGE_TYPE_X runtime error occurs in the LRSSMU36 include program in the SAPLRSSM ABAP program of the RSSM_OLTPSOURCE_SELECTIONS function module, proceed as described in the solution below.
This dump occurs if you try to open an InfoPackage for a DataSource/source system combination for which an initialization terminated incorrectly and a new INIT with overlapping selections was executed without the delta-administration being cleaned up.

The dump can also occur if you import a system copy/backup into only one of the two BW/OLTP systems without first deleting all delta queues for this BW/OLTP combination because the delta administration is always inconsistent.

A similar dump occurs in
perform "RSM1_CHECK_FOR_DELTAUPD in the LRSS1F11 include if the source system does not recognize any more inits (the roosprmsc and roosprmsf tables are empty) but if there are still entries in the RSSDLINIT/RSSDLINITSEL tables in the BW system.
This is the same as the problem described in Notes 424848 and 591382.

Other terms

Dump, include LRSSMU36, RSSM_OLTPSOURCE_SELECTIONS, MESSAGE_TYPE_X
Init, delta queue, system copy, backup, initialization, InfoPackage
RSM1_CHECK_FOR_DELTAUPD, LRSSMU36, LRSS1F11
RSSDLINIT, RSSDLINITSEL, RSSM_OLTP_INIT_DELTA_UPDATE

Reason and Prerequisites

This problem is caused by a program error.


Solution


You can implement this correction only for load times from an OLTP system because transaction RSA7 is used for the delta administration/deletion.
For a DataMart, you may have to delete using transaction SE16 or a native SQL.

1. The entries for the initialization in the BW system are contained in the RSSDLINIT table for the DataSource/source system combination. Compare these with the entries in the ROOSPRMSC table in the OLTP system.
2. If there are NO entries in the RSSDLINIT table in BW, use transaction RSA7 to delete the delta queue for this DataSource/BW application combination in the source system (OLTP). For a DataMart source system, manually delete the entries in the ROOSPRMSC and ROOSPRMSF tables for your DataSource using transaction SE16 or a native SQL on the database. A DataMart can be identified by the DataSource that starts with '8', and by the fact that you CANNOT find it in RSA7 of the source system.
3. If the RSSDLINIT table in the BW system already contains entries, check the requests listed there in the RNR column in the monitor (transaction RSRQ). Compare these entries with the entries in the ROOSPRMSF and ROOSPRMSC tables with the INITRNR field. If, in the ROOSPRMSF and ROOSPRMSC tables for your DataSource source system combination, there are more entries with different INITRNR numbers, use transaction RSA7 in an OLTP source system to delete all entries and then use the RSSM_OLTP_INIT_DELTA_UPDATE report mentioned in the next section. For a DataMart source system, delete the entries that you cannot find in the RSSDLINIT table using the procedure described above.
4. Read also Notes 591382 and 424848. The errors described there also occur if you delete entries using transaction RSA7 in the source system but there is no RFC connection to the BW system. In the source system, there are no more entries in the ROOSPRMSC and ROOSPRMSF tables, but in the BW system, there are still entries in the RSSDLINIT and RSSDLINITSEL tables. Execute the RSSM_OLTP_INIT_DELTA_UPDATE report and then delete all init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.
5. When you have completed this procedure, you should be able to create a new InfoPackage or open an InfoPackage.

You can then open the InfoPackage again.
Check that there are no more entries in the
'Scheduler'/'Initialization options for source system' menu

If you do find some entries, delete them.

You can then start a new initialization.

If, despite the first incorrect init, you want to be able to create a second init with overlapping selections, which means that this dump will then occur, enter a detailed description of your procedure in a customer message and send it to Development. SAP has never been able to reproduce this behavior, therefore, a great deal of testing and the option to debug in your system would be required.


среда, 11 марта 2015 г.

На новой системе проблема при загрузке файлов, с признаком Material

Если запрещённыые символы:
 t-Code RSKC = ALL_CAPITAL*



t-Code SPRO - SAP NetWeaver - Business Warehouse - Общие параметры настройки - Настройка представления номера материала

На новой системе ошибка загрузки текстов. rsdmd 194

Тема.

Включаем t-Code RSKC - ALL_CAPITAL_PLUS_HEX


А вообще-то:

Note 1580561:Error RSDMD194 when loading BW master data


Symptom
Your BW master data load fails with the following RSDMD 194 error, viewable in the Details tab of the load monitor:
  • <characteristic_name>: Data record <number> ('........'): Version '........ ' is not valid
    Message no. RSDMD194
There may be some additional errors mentioned in the monitor, such as:
  • Too many error records - update terminated
    Message no. RSM2706
  • Error occurred in UPDATE_INFOCUBE for data target <technical name>
    Message no. RSAU499

Environment
  • Business Warehouse BW
  • Business Intelligence BI

Reproducing the Issue
Run a BW masterdata load of records which contain characters that the BW system doesn't recognise.

Cause
  • The error message RSDMD 194 means that you tried to load non-permitted characters into the BW system. Control characters from HEX00 to HEX1F are forbidden characters as per SAP Note 1075403 & such characters are not allowed in BW.
  • Often this issue is due to the fact that lowercase characters are not allowed in BW by default.

Resolution
In general, to resolve this RSDMD 194 problem, you would either:
  • remove the non-permitted character(s) in the source system of the particular load,
  • or you should change/convert these values to something acceptable using an ABAP routine within the transfer rules/update rules/transformation for each affected master data load (refer to those relevant SDN threads which contain sample code).
For the lowercase characters restriction, you must permit such characters at characteristic/InfoObject level as follows:
  1. Goto tcode RSD1
  2. enter the relevant characteristic/InfoObject name
  3. click the Change button
  4. in the General tab of the resultant screen, tick on the "Lowercase Letters" checkbox (see below screenshot).
  5. Do likewise for all other characteristics mentioned in the RSDMD 194 error message of the failing request.
  6. Reactivate the relevant DataSource(s) before reloading the data.
char_lowercase_flag.bmp

Keywords
PSA, masterdata, error 4, RSAR 119, RSM2 704, RSM2 706, RSDMD 190, RSAU 499, BRAIN060, BRAIN 060, BRAIN60.

References
This document refers to:
CSS SAP Notes
1373402Issues with invalid characters or SID Generation
1075403Unallowed characters and ALL_CAPITAL
173241Allowed characters in the BW System

На новой системе не собирается поток до\после от объекта

Надо поставить галку для исходной системы (левый желтый значок - Присвоение исходных систем):