David's Untitled Life

DBIF_RSQL_INVALID_RSQL short dump

Tue, 05 Jan 2010 06:36:16 +0000

when we trying to retrive data by SE16 etc, we input tons of single values and might come into DBIF_RSQL_INVALID_RSQL short dump.

This is not a SAP error, it's due to open sql limitation.

You can find more detail in Note 13607 Termination of an ABAP with DBIF_RSQL_INVALID_RSQL

[Collection]Master Data IDoc Message Type List

Thu, 26 Feb 2009 00:55:33 +0000

http://www.erpgenie.com/sapedi/message_types_masterdata.htm

General	Message types / IDoc types / BAPI
Vendor	CREMAS / CREMAS02
Customer	DEBMAS / DEBMAS03
Accounting	Message types / IDoc types / BAPI
G/L account	GLMAST / GLMAST01
Cost center	COSMAS / COSMAS01
Cost element	COELEM / COELEM01
Cost center group	COGRP1 / COGRP01
Cost element group	COGRP1 / COGRP01
Activity type	COAMAS / COAMAS01
Activity group	COGRP1 / COGRP01
Activity price	COACTV / COACTV01
Profit center	PRCMAS / PRCMAS01
Profit center group	COGRP1 / COGRP01
Profit center account group	COGRP1 / COGRP01
Logistics	Message types / IDoc types / BAPI
Article master	ARTMAS / ARTMAS02 / RetailMaterial.Clone
Additional	MMADDI / MMADDI01 / RetailMaterial.SaveAdditionalReplicas
Product catalog	PRDCAT / PRDCAT01
Product catalog item	PRDPOS / PRDPOS01
Price list	PRICAT / PRICAT01
Assortment	ASSORTMENT / ASSORTMENT01 / Assortment.SaveReplica
Material master	MATMAS / MATMAS03 - (See Template)
Service master	SRVMAS / SRVMAS01
Characteristic	CHRMAS / CHRMAS02
Class	CLSMAS / CLSMAS03
Classification	CLFMAS / CLFMAS01
Document	DOCMAS / DOCMAS04
Purchasing info record	INFREC / INFREC01
Conditions	COND_A / COND_A01
Order book	SRCLST / SRCLST01
Change master	ECMMAS / ECMMAS01
Bill of material	BOMMAT / BOMMAT01
Document BOM	BOMDOC / BOMDOC01
Work breakdown structure	Project / PROJECT01
Human Resources	Message types / IDoc types / BAPI
PA object type person	HRMD_A / HRMD_A03
PD object types	HRMD_A / HRMD_A03
Basis	Message types / IDoc types / BAPI
User master record	USERCLONE / USERCLONE01 / User.Clone

Unit of Measurement notice when using ALE/IDoc

Wed, 25 Feb 2009 22:17:01 +0000

When we need to pass UoM to SAP by IDoc, we need to pass ISO Code, not internal UoM format.

The value is stored in T006 table.

Detailed info: Note 69063

issue of importing info record using INFREC IDoc

Wed, 25 Feb 2009 21:51:50 +0000

INFREC don't update net price of info record, because it's stored in condition table KNOH and KNOP.

We have to load price condtion using CON_A after INFREC.

BAS Business Adress Service

Sat, 14 Feb 2009 00:25:46 +0000

http://help.sap.com/saphelp_nw04/helpdata/en/c8/13b237b9a9a968e10000009b38f8cf/frameset.htm

Customer/Vendor Message type:ADRMAS
Process Code: BAPI

失手造成无法登陆服务器，贱手！

Tue, 03 Feb 2009 05:52:30 +0000

为了演示SUSR0001这个logon sap的customer exit，我做了实现，可惜手太快，判断USER的时候，写的是小写，如果不是XXX，则全部CALL 'SYS_LOGOFF'，结果可想而知，谁也别想登陆服务器了。
于是我直接进入到DB一层（我们用SQL SERVER2005）把REPOSRC中的ZXUSRU01删除，可是不行。
我发现，SAP实现一个customer exit的active&inactive是通过对表TFDIR中的CLIENT字段操作的，如果激活状态，字段值为C，如果是INACTIVE状态，字段值是空，我直接改了DB，还是不起作用。
正当我在折腾version management system表的时候，我突然想从sap management console试试。
找到R3SysLog，然后右键，all task-> analyse 登陆的画面弹出来了，输入用户名密码，直接进入了R/3...OMG，终于不用重装了。

No logical path has been specified

Tue, 13 Jan 2009 07:54:12 +0000

When loaded WM bin master data by program RLPLAT00 using LSMW, i got error message "No logical path has been specified" at speficy files step.

As a result of RLPLAT00 needs logical file. We can run it directly and get this result from selection screen.

More detail info, please refer NOTE 753511

Summary

Symptom

The system issues an error message concerning the logical path or file when you perform the "Specify files" step in the Legacy System Migration Workbench (transaction LSMW), even though you have made the correct assignment in transaction FILE.

The error messages are listed below:

The logical path <PATH> does not point to the physical directory.

The logical file <FILE> is not assigned to the physical file.

The logical path <PATH> does not exist.

The logical path <PATH> does not exist for this operating system.

A logical path was not specified.

Other terms

Logical path, logical file, transaction FILE, LSM Workbench, /SAPDMC/LSMW_OBJ_060, batch input, direct input, BI, DI

Reason and Prerequisites

Some import interfaces that you can also use with transaction LSMW work with logical path and file names.

Transaction LSMW itself, however, works with physical file names. To be able to transfer the LSMW file with the converted data to the import program, you must specify a logical file name for the file with the converted data in addition to the physical file name. In this case, in the step "Specify files" for the converted data file, you obtain additional fields in which you must enter the logical path name and file name (choose "Change entry" for the converted data).

Solution

The error messages may be due to several causes. Check the following:

Have you maintained the logical path and logical file name and have you assigned them to the physical file specified in the "File" input field of transaction LSMW?
These settings are maintained in transaction FILE.

Note that you must also make an assignment to the physical path for the full specification of a logical path in transaction FILE. You must make this assignment for all potential syntax groups (groups of operating systems with the same syntax for file paths). Refer to the documentation for transaction FILE for additional information.

When you use logical file and path names, you must specify the name of the physical file with its path. If you have not specified any directory, you cannot assign any directory to the logical path in transaction FILE. In this case, the system uses the SAP Home directory on the application server by default. Bear in mind that the file name must not exceed the maximum length of 45 characters, including the path.

Up to LSMW Version 1.7.2 (*):
If the logical file name specified does not point to the physical file (although it should do so), the system adjusts the logical file name, that is, the information in transaction FILE is changed to the entries made in transaction LSMW. This may lead to unwanted side effects if the logical file is also used somewhere else. Therefore, SAP recommend that you always use separate logical paths and file names for transaction LSMW (the problem is corrected as of LSMW version 1.8.0, see below). If the logical file does not exist yet, it will be created upon request.

As of LSMW Version 1.8.0 (*):
Although the settings of the logical file are checked, they are no longer adjusted automatically as in Version 1.7.2 (see above). If there are inconsistencies, the system issues an error message. If the user is authorized to maintain logical paths and file names (as for transaction FILE: "Maintenance authorization for cross-client tables"), transaction LSMW can create the logical path, the file name and the file. Due to this automatic generation, the user no longer needs to make adjustments in transaction FILE. Therefore, we especially recommend this procedure.

(*):
To display the version of transaction LSMW, select "Extras" --> "Display LSMW version" in the main menu of the initial screen.
You should also bear in mind that as of Basis Release 6.20, that is, as of LSMW Version 4.0, transaction LSMW is no longer an add-on but is delivered with the standard system.

BAPI_CUSTOMER*

Fri, 02 Jan 2009 11:34:37 +0000

The BAPIs of the function group V02D are intended exclusively for use in the SAP Online Store and the SAP Internet Sales R/3 Edition, that is you can create or change consumers from the SAP Online store and SAP Internet Sales R/3 Edition in the R/3 system. You cannot use them to create or change customer masters or consumers in the standard system; you can only do this using ALE or Batch Input.
When you use the above-mentioned BAPIs outside of SAP Online Store or SAP Internet Sales R/3 Edition, or with customer master records that were created or edited outside of the SAP Online Store or SAP Internet Sales R/3 Edition, there is a danger that you will lose data.

Cross-system company code 1000 does not exist

Wed, 24 Dec 2008 03:38:08 +0000

如果使用了ALE/IDoc来分发数据，就可能涉及cross-company code

配置路径

SAP NetWeaver->Application Server->IDoc Interface / Application Link Enabling (ALE)->Modelling and Implementing Business Processes->Global Organizational Units

Global Organizational Units

There are global organizational units which must be named the same in all systems to avoid any errors occurring in the distributed environment. Local organizational units are assigned to global organizational units in the individual systems.

There are global organizational units for the organizational units:

- Company code

- Business area

If you want to use ALE, you have to assign the local organizational units to the global organizational units in your systems to ensure that they are used consistently in the distributed environment.

Cross-System Company Codes

Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.

When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields. When receiving this kind of IDoc the reverse conversion takes place on the target system.

In this section you maintain the cross-system company codes and allocate them to the local company codes.

Recommendation

- The use of cross-system company codes and business areas in distributed financial accounting is a provisional measure. SAP reserves the right to replace this in a future release with a tool that allows a conversion for all the organizational units of the SAP system.

- Therefore SAP recommends that you choose consistent identifiers for the company code and the cross-system company code.

Activities

1. Create a cross-system company code.

2. Assign the cross-system company code to a chart of accounts to which it is also assigned on the central system.

This setting is needed on the decentral systems in order to determine the chart of accounts of the company code on the central system.

3. Assign cross-system company codes to the local company codes.

Specify the identifiers of the relevant cross-system company codes for each of the individual company codes.

SAP Idoc control record信息

Tue, 09 Dec 2008 09:36:27 +0000

http://www.informatik.fh-wiesbaden.de/~werntges/lv/edi/specs_EN/SAPdoc/IDoc_d.htm