Age: 170 Joined: 04 Oct 2007 Posts: 1218 Location: Санкт-Петербург
Posted: Wed May 14, 2008 11:22 am Post subject:
Например, Вы хотите добавить search-help к полю Street/House number (Рис. 1 )
Нажимате F1 на поле и выясняете, что элемент данных AD_STREET
Заходите в этот элемемент данных. Вас интересует блок Search-Help.
Для этого элемента данных уже существует SH c именем STRT_NAME (Рис. 2 ).
Если бы это поле было пустым, то потребовалось получить ключ на модификацию этого элемента данных и добавить собственный Search-Help, который тоже надо создать.
Например, существующий STRT_NAME использует представление M_STRTA в качестве стправочника адресов. (Рис.3 ) Может вам достаточно заполнить таблицы, входящие в STRT_NAME своими значениями?
В моём случае, для элемента данных AD_STREET уже сусчествует другой Search Help, который включает в себя Search Help с именем STRT_NAME.
Но, дело в том, что никакой Search Help для поля Street не запускается (No input helps is available)
Age: 170 Joined: 04 Oct 2007 Posts: 1218 Location: Санкт-Петербург
Posted: Wed May 14, 2008 6:50 pm Post subject:
andrej_s wrote:
Но, дело в том, что никакой Search Help для поля Street не запускается (No input helps is available)
Подозреваю, что он не запускается, потому что справочник улиц не ведется и таблицы пустые.
Попробуйте создать интервалы
SRN1 Number range maintenance: ADRCITY
SRN2 Number range maintenance: ADRSTREET
SRN3 Number range maintenance: ADRPSTCOD
и завести город и улицы
SR10 Create City
SR11 Change city
SR12 Display city
SR13 Area-Dependent Help
SR20 Create street
SR21 Change street
SR22 Display street
SR30 Create postal code
SR31 Change postal code
SR32 Display postal code
Age: 170 Joined: 04 Oct 2007 Posts: 1218 Location: Санкт-Петербург
Posted: Mon May 19, 2008 1:34 pm Post subject:
Note 810124 - SAP regional structure number ranges
Quote:
Summary
Symptom
This note provides help when you maintain the number ranges for the SAP regional structure. The number range objects are ADRCITY, ADRSTREET and ADRPSTCODE and can be maintained using transaction SNRO.
Other terms
BAS_REGIONALSTRUCTURE
Solution
You can maintain the objects of the regional structure either manually using transactions SR10, SR11, SR20, SR21, SR30 and SR31 or by using the RSADRLSM02 program (see SAP Note 132948).
The postal codes may have different formats depending on the country in question. We therefore recommend the following delivered default Customizing.
UDP: Вы просили ноты:
Note 132948 - Transfer programs for the R/3 regional structure
Quote:
Summary
Symptom
Importing data to the standard SAP regional structure.
Other terms
City file, LSM workbench
BAS_REGIONALSTRUCTURE
Reason and Prerequisites
As of Release 4.0, a regional structure exists in the standard R/3 System (see Note 98050). You can use it to check whether the postal data for an address (postal codes, cities and streets) is correct.
The regional structure is empty when delivered by SAP.
This means that the customer is responsible for obtaining the country-specific data for filling the regional structure and then maintaining it.
Up to Release 4.5A, only transactions for the individual maintenance of regional structure data were available. Importing mass data has not been supported directly up to now.
Solution
For the automatic import of mass data to the regional structure, you can use report RSADRLSM02 together with the LSM workbench (as of Version 1.0).
The report is delivered in the standard system with Release 4.5B and cannot be executed under older releases.
Report RSADRLSM02 and also the entire procedure for importing and for maintaining the standard SAP city file are made available and maintained by the central address management. Therefore, if you encounter problems, create a SAPNet - R/3 Frontend (OSS) message for component BC-SRV-ADR. Only those errors directly concerned with the functions of the LSM workbench are to be assigned to component XX-LSM.
A completely revised version of report RSADRLSM02 can be found in the correction instruction for Note 333899 and must be used.
Procedure
1. Source data
First of all you have to obtain reference data that is to be imported to the city file from a third-party provider. Since there are many providers of such regional structure data, you should place importance on the following criteria when making your selection:
The provider should not only make current regional structure data available but also be able to deliver difference data at regular intervals. This is important if you want to keep your city file up to date. It is of course possible to continually initialize the regional structure and to import the current data again completely or to overwrite the legacy data somehow with new data. However, such a procedure is complicated and the quality of the data or the quality of the addresses to be checked against the regional structure will suffer as a result.
The streets and cities contained in the reference data must have a unique key.
If city districts or PO boxes are also specified in the reference data, they must have a key unique for each city. If no keys exist in the city districts or PO boxes, these cannot be processed.
All street sections belonging to a street must have the same street key.
In all city districts, PO boxes and street sections or streets the key of the city, to which the objects are assigned, must be specified.
It is desirable that the key of the city, in which the respective postal code is used, is also specified in all the postal codes. Here, it is allowed when postal codes occur more than once (each with different or even the same cities).
The structure and the data structure of the source data should be documented. Using the data without this information causes difficulties.
Once you have settled on a provider, you will have to always update the city file using only the data from that particular provider in the future. If you want to change the provider, you will have to delete all the data imported thus far from the city file and all references to it from the addresses checked against the city file (using report RSADRLSM01) before you import the new data.
2. Implementing the source data
Before the source data can be maintained in the city file, it has to be converted into a format which can be read by report RSADRLSM02.
This can be done easily using the LSM workbench (as of version 1.0), which is made available free of charge to customers and partners on request (see also Note 101014).
Details about how the source data is to be implemented and points that have to be taken into consideration during this process are described in Note 334096 for the LSM workbench as of Version 1.5 or in Note 333954 for Version 1.0 of the LSM workbench.
3. Automatic maintenance of city file using report RSADRLSM02
Use report RSADRLSM02 for maintaining the converted data to the standard SAP city file.
The report expects the logical file names of the data to be imported as an entry. These can be defined directly using the LSM workbench. The logical file name for the flow log must also be specified (see report documentation RSADRLSM02). It is also mandatory that the country, for which data is to be created, and the default creation language are specified.
A detailed description of all interface parameters can be found in the program documentation.
You can choose whether to maintain regional structure objects either individually or together with other regional structure objects. That is, you can for example either first process all cities and then maintain streets in a second run or process streets, postal codes, city districts and so on together in a run.
Since dependencies can exist between the objects (for example, a street can only be created once the corresponding city has also been created), it is nevertheless useful always to process all objects together in a run.
Depending on how you implemented the source data using the LSM workbench, report RSADRLSM02 creates, updates or deletes objects from the city file and makes sure that no inconsistencies occur. Errors are logged.
The report should be started in the background because processing can take several hours. Once processing has started no one else should make changes to the regional structure as doing so could lead to inconsistencies and perhaps even a processing termination.
When importing data to the city file for the first time, you must initialize it beforehand to prevent conflicts from occurring with the legacy data. You can delete possibly existing data before importing data for the first time using report RSADRLSM01 (when somewhat larger volumes of data are involved, this should be executed as a background process using the version of the report as available in the correction instruction from Note 310215).
Restrictions
When updating the dataset, the same data source must always be used. That is, you must not change from using one provider's postal data to another. However, if this is necessary, all the regional structure data created so far must be deleted for the new country to be supplied. Only then can the data of the new provider can be imported.
The regional structure data can only be maintained per program run in one language: the default creation language. That is, it is not possible to maintain city or street names in several languages at the same time, for example.
The LSM workbench must have Version 1.0 or higher.
The number range intervals for objects ADRPSTCODE, ADRCITY and ADRSTREET for the external number assignment must remain unchanged as compared to the status delivered by SAP. In each case, this involves interval 01. Changes can result in objects not being created completely not being created at all or a program termination occurs.
Errors or problems during execution
Providing the problems are not directly connected with the functions of the LSM workbench, assign your problem messages to the component BC-SRV-ADR in the SAPNet - R/3 Frontend (OSS). Unless another component can be used from a possible system message or the error does not directly have anything to do with the import program.
ой, а у уменя при создании индексов возикает проблема:
Индес города не отображается на карточке делового партнера как справочник.Все остальные с успехом создаються данные.
На карточке это поле ADDR1_DATA-POST_CODE1 Почтовый индекс,
а при Создании Индекса в тр. sr30 - это POST_CODE, (и этого поля на карточке нет)
а мне очень нужно сделать связку город-индекс-улица.
Так же не ведётся почему то на карточке и поле Тип улицы
ПОдскажите что сделать, чтоб отображался справочником поле POST_CODE1
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG. SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG. Every effort is made to ensure content integrity. Use information on this site at your own risk.
