Ansicht
Dokumentation

CRM_TERRMAN_IMP_I_TEMPLATE - Template for Importing Territory Objects

ROGBILLS - Synchronize billing plans Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.

Title

Template for Importing Objects for Territory Management

Purpose

You can use this report as a basis for creating your own report, to load territories and their structures from another system to the CRM Server using an ASCII file.

Alternatively, you can maintain territories manually in the Territory application in the CRM WebClient UI.

Note: CRM_TERRMAN_IMP_I_TEMPLATE is a template report. Do not change it. Instead, copy it to your own report and adapt your report according to your requirements.

Integration

In a Mobile Sales scenario, you can distribute objects for Territory Management to the mobile client for display.

See under Selection for more details.

Prerequisites

Before importing the territory data, ensure that

You have maintained the territory levels in Customizing under Master Data -> Territory Management -> Define Territory Hierarchy Levels

The structure of the technical territory names correspond with the definition in Customizing

The contents and the structure in this report correspond with the contents and the structure of the ASCII import file

Redefine the structure of the import file LTY_RAW_RECORD

Redefine the update of the territory attributes: move from GS_IMPORT to GS_TERRATTRIB

You have maintained the Ruleset GUID to indicate the rule set under which rules should be created - in the file (for example: Import.txt) your are importing.

The following example (also used in the IMG activity Define Territory Hierarchy Levels under Customer Relationship Management by choosing Master Data -> Territory Management), is used to illustrate how the ASCII file should be structured.

The ASCII file for this report template uses the following line structure, which consists of the territory hierarchy ID plus the brick ID. Note that the brick is an attribute, not a level, so it is not included in the territory hierarchy in the example above.

A1B01C001D0000001ZB100 (for ABC Inc., Bottles, North, Boston, Brick ZB100)

A1B01C001D0000001ZB101 (for ABC Inc., Bottles, North, Boston, Brick ZB101)

A1B01C001D0000002ZB200 (for ABC Inc., Bottles, North, New York, Brick ZB200)

A1B01C001D0000002ZB201 (for ABC Inc., Bottles, North, New York, Brick ZB201)

A1B01C002D0000003ZB300 (for ABC Inc., Bottles, South, Miami, Brick ZB300)

A1B02C001D0000001ZB400 (for ABC Inc., Cans, North, Boston, Brick ZB400)

Features

Selection

Specify a file name including the directory path, for example: C:\TEMP\IMPORT.TXT
Specify the validity period end of territory hierarchy, suggestion: infinite
Specify the language in which the names of territory objects appear
If you are running the report for the first time, do not select Create Territory Objects. The report will then run in test mode. After the report has run, check the log.

If there are no errors, run the report again and select Create Territory Objects to update the database. We recommend that you run it in the background.

For better performance, we recommend that you run this report without downloading the territory objects immediately to the mobile clients. In this case, do not select Download BW/Mobile Immediately.

However, if the territory objects should be downloaded straight away, select this field.

After the import has been completed successfully, start the initial download of the objects to the mobile clients in the IMG under Territory Management -> Data Transfer -> Download Territories to CRM Mobile.

Standard Variants

Output

After you run the report, the system issues a log that lists the territory objects and their hierarchical position.

Activities

Example

General Data in Customer Master CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.

Length: 4677 Date: 20240520 Time: 060233 sap01-206 ( 68 ms )

Ansicht Dokumentation