How To Fix E7101 - Jur.Code-Transfer vom Vertrag z. Anschlussobjekt für Mandant &1 nachholen

SAP Error Message - Details

• Message type: E = Error

• Message class: E7 - IS-U master data

• Message number: 101

• Message text: Jur.Code-Transfer vom Vertrag z. Anschlussobjekt für Mandant &1 nachholen

This message is only relevant when you use client &V1& <LS>Tax
Jurisdiction Codes</> (for determining tax rates in the USA).
If your client only contains a test company code that contains the
settings for tax jurisdiction codes, but does not use them, then you
can ignore this message.

Was verursacht dieses Problem?

During the upgrade, a company code was found in client &V1& that
contains &V2& as the country key. The use of tax jurisdiction codes is
active in this country key.
Starting with IS-U/CSS Release 4.61, the tax jurisdiction code is saved
in the address of the connection object, and no longer in the data for
the IS-U contract. Report ISU_TRANSFER_JDC_TO_COADDR is available to
transfer existing tax jurisdiction code, which saves you from having to
enter them again manually. This report automatically copies the value
of field <LS>Tax Jurisdiction Codes</> from all IS-U contracts to the
address of the connection object, assuming this is possible and
logical.
This report was not run in client &V1& before the upgrade, however. You
can also run the report after the upgrade. We recommend running the
report before you go live, because the following problems could occur
during production operations:
The report blocks individual contracts and connection objects, which
means clerks could be prevented from changing this data (especially
when entering move-ins and move-outs in the system)
The report cannot process contracts or connection objects that are
currently blocked by a clerk
These cases are output in the report log and have to be postprocessed
by restarting the report again for the failed connection objects after
the clerk has released the data.
Before you run the report, missing values in field <LS>Tax Jurisdiction
Code</> can result in error messages in the following cases (examples):
When changing technical master data (connection object, premise,
installation)
During move-in/move-out processing
This will result in unnecessary additional work and complications that
could prevent you from running the report.

Wie behebe ich diesen Fehler?

Start report ISU_TRANSFER_JDC_TO_COADDR before you go live, if
possible. If your tight schedule does not allow it or it was simply
forgotten, we recommend running the report outside of your clerks'
regular working hours (at the weekend, for example), as the report will
have a long runtime if you have a large number of contracts and
connection objects.
Parallel execution of the report is possible. If the size of your
dataset requires parallel execution, we recommend proceeding as
follows:
Divide the total number of existing connection objects into n intervals
of approximately the same size.
Start report ISU_TRANSFER_JDC_TO_COADDR n times, once for each
interval.
Please note that if you choose parallel execution of the report, you
are responsible for ensuring that the report actually processes all the
connection objects. When you divide the set of connection object
numbers into intervals, you will have to make sure that all the
intervals are processed and that all the intervals together seamlessly
cover the complete set of connection objects.
You should always check the logs from the report runs to make sure that
all the connection objects in the run could be processed correctly.
If a business partner (for example) is blocked by a clerk (or by a
parallel run), an entry is written to the log. If you need these data
records, you will have to manually postprocess them by starting the
report again for these connection objects.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE