A manual tax entry is created and the tax is calculated. If the tax due date is changed, the tax is not calculated newly.

Reason and Prerequisites

Programming Error
Solution

Please provide the correction as hotfix.

The tax code warning message for the chain transaction in customer invoice vanishes too quickly. It only appears again changing the instance of customer invoice.
Other terms

Customer Invoice;
Reason and Prerequisites

Programmerror.
Solution

This correction has to be shipped as a hotfix. This correction will be included in Feature Pack 2.0 SP02 and higher SP.

Related:

1. ByD_HF: Cancel Invoices after migration to full scopeSymptom For the invocies created in partial use, some restrictions...
2. BYD_HF: Scope determination (partial use)Symptom Partial Use – the Check for the scope has...
3. BYD_HF: Wrong CIR Reference send to AccountingSymptom You are using ByDesign Workcenter Customer Invoicing and have...
4. BYD_HF: Provision does not get printed if emptySymptom You are using Customer Invoicing and find that for...
5. BYD_HF: Output Settings: F4 help of FormTemplate not workingSymptom You are using Customer Invoicing and are selling to...
6. BYD_HF: B2B message not send correctly using mass invoicingSymptom You are using Customer Invoicing with B2B communication and...
7. BYD_HF: Dump when printing an invoice w/o taxation termsSymptom You are using Customer Invoicing and encounter a system...
8. ByD HF: Properties for Custoemr Invoie Request in Manual InvSymptom The creation of a document in the Manual Invocie...

Hotfix 21206:
tax line item reconciliation: Payments with transfer of deferred tax are not reported correctly, if it is a full payment and if the corresponding invoice has two different tax groups in tax register. Two different tax groups are written in tax register for example if one of two invoice items was discount relevant.
Weitere Begriffe

deferred tax, tax reconciliation
Ursache und Voraussetzungen

Program error
L鰏ung

Implement the hotfix 21206

Under the view management tab, you deassign a couple of characteristics from the view, so that they are not visible at the Catalog Search Engine. You add a few items from these views to SRM shopping carts. The OCI data will not hold the characteristics that have been deassigned for this view.
Other terms

Characteristics, OCI, Add to Basket.
Reason and Prerequisites

The view filter was being applied during the OCI navigation which is not required as all the fields have to be passed to SRM.
Solution

Please import the corresponding support packs or implement this note.

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component CCM SAP Catalog Con…|
| Release 200_640 Until SAPK-26414INCCM |
| Release 200_700 Until SAPK-27014INCCM |
————————————————————————
1. Go to transaction SE80.
2. Choose ‘Class/Interface’ from the dropdown in the ledt panel.
3. Provide class name as /CCM/CL_CATALOG_MANAGER and hit enter.
4. Under the ‘Atrribute’ tab – Choose attribute GT_VIEW_GUID.
5. Remove the ‘Read-only’ flag from the attribute by unchecking the same.
6. Save and Activate the changes.

The user logging into CCM Search Engine has a role with two or more view assignments. If one of the views assigned has a set of characteristics deassigned from the view, then this deassignment is applied for all the views assigned to the role.
Other terms

Views, Assign, deassign, characteristics, Search Engine, Role, assignment.
Reason and Prerequisites

The characteristics were filtered based on all views irrespective of the item belonging to the view or otherwise.
Solution

The solution will be included in the next SP. Please implement this note for prior solution.

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component CCM SAP Catalog Con…|
| Release 200_640 All Support Package Levels |
| Release 200_700 All Support Package Levels |
————————————————————————
1. Goto SE80.
2. Choose class /CCM/CL_CATALOG_HANDLER.
3. Choose Method GET_ITEMS in edit mode.
4. Choose the ‘Signature’ button. Open in edit mode.
5. Add a parameter -
PARAMETER: IV_OCI_DATA.
TYPE: IMPORTING.
OPTIONAL: CHECKED.
TYPING METHOD: TYPE
ASSOCIATED TYPE: ABAP_BOOL.
DEFAULT VALUE: ABAP_FALSE.
6. Save and Activate the changes.

If you select on the outbound delivery list advanced search for sales order ID, inbound delivery ID, inbound delivery notification ID or purchase order ID you can get too much results which don’t match to the entered selection.
A wrong ship_to_location may also be shown.
Other terms

OUTB_DEL_LIST A1S_ODE_LST_OVERVIEW CL_A1S_ODE_OWL_SEL_MAPPING
Reason and Prerequisites

The FSI view restriction rules were not set in the correct way. As consequence it was searched for any reference with the entered ID independant of the semantic (reference type code).
Solution

The correction is fixed with hotfix 21393 and shipped
in correction bundle for SP2 with M2SK014872,
as hotfix for SP1 with H1EK003544 and
as hotfix for SP0 with H0EK007901

No tax transaction key exists for billing document and country US
Other terms

BILL_ACC_IF108,
No tax code has been found for this tax item and country US

Reason and Prerequisites

Progamming error

Solution

This error is fixed from SP19 onwards. For SP08 – SP18
Please download the latest patch from service market place
following note 880749.

Related:

1. General Ledger Line items report for China and FranceSymptom General Ledger line items report for China and France,...
2. General Ledger Line items report for China and FranceSymptom General Ledger line items report for China and France,...
3. SAP-BP: Error R11 401 during address creation for countrySymptom When creating an address using BUPA_ADDRESS_ADD (or any application...
4. Tax is calculated for other item with “single-use” TECSymptom Create a sales order with one item and the...
5. Tax event, tax code changes to FranceSymptom Tax code description for the tax code 500 to...
6. Empty P45 datasetsSymptom It was possible to create empty datasets for P45...
7. Confirmation date & quantity status determined wrongSymptom BYD_HF: Confirmation date & quantity status determined wrong Other...
8. Field ACCNT_NO is not populated for External Tax CalculationSymptom The taxes are different in CRM and ECC.The reason...

Short dump SYSTEM_SHM_AREA_OBSOLETE in class /APC/BA_REPORT_BUFFER and method GET_REPORT_LATENCY.
Other terms

BAR BO
Reason and Prerequisites

The problem occurs if Analytical Sets are activated while end-users are connected to the ByDesign System.
Solution

The problem is fixed with ByDesign hotfix 21452.
FP2.0 SP0
Ensure that transport request is imported: H0EK008022.FP2.0 SP1
Ensure that transport request is imported: H1EK003730.FP2.0 SP2
Ensure that transport request is imported: MGGK031452.

When you create an installed base (Transaction IB51) you can use another
installed base as copy template (create with reference). If this
reference installed base has text items the system does not copy the
texts into the new installed base. This is corrected with this note.
Other terms

SAPLIBOF, IB52, IB53
Reason and Prerequisites

The problem is caused by a program error.
Solution

Implement the advance correction.

Missing test functionality
Other terms

Price Masterdata
Condition Maintenance
Reason and Prerequisites

Important functionality worth to be tested with an automated test
Solution
1. Apply the manual pre-implementation steps.2. Apply the attached correction instruction (SNOTE)

————————————————————————
|Manual Pre-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_AP SAP Application…|
| Release 700 Until SAPKNA7018 |
————————————————————————

1. Create the structure /SAPCND/TST_ATTRIB_VALUE_EXT with the following components:a) FIELDNAME TYPE /SAPCND/FIELDNAMEb) FIELDNAME_INT TYPE /SAPCND/FIELDNAMEc) VALUE TYPE /SAPCND/ATTRIB_VALUE_EXTERNALd) VALUE_INT TYPE /SAPCND/ATTRIB_VALUE_INTERNAL2. Create the table type /SAPCND/T_TST_ATTRIB_VALUE_EXT with line type /SAPCND/TST_ATTRIB_VALUE_EXT.3. Create the structure /SAPCND/TST_DB_INSERTED_VALUES with the following components:a) ROLLNAME TYPE ROLLNAMEb) ATTRIB_VALUE TYPE /SAPCND/T_ATTRIB_VALUE_INT4. Create the table type /SAPCND/T_TST_DB_INSR_VALUES with line type /SAPCND/TST_DB_INSERTED_VALUES.5. Create the structure /SAPCND/WS_TYPE with the following components:a) HSESSION TYPE /SAPCND/MAINT_SESSION_IDb) APPLICATION TYPE /SAPCND/APPLICATIONc) WSI_INT TYPE DATAd) T_WS_INT TYPE DATAe) WSI_EXT TYPE DATAf) T_WS_EXT TYPE DATAg) T_SKU_WS_INT TYPE DATAh) T_SKU_WS_EXT TYPE DATA
______________________________ ______________________________
6. Add the following component to the structure /SAPCND/TST_SESSION_DATA:a) WS_TYPE TYPE /SAPCND/WS_TYPE STRU
at position 4.7. Add the following elements to the structure /SAPCND/TST_APPLICATION_DATA:a) WS_NAMES TYPE /SAPCND/WORKING_SET_NAMES STRU
at position 3.b) WS_TYPE TYPE /SAPCND/WS_TYPE STRU
at position 4.c) ATTR_VALUE_TABLE_EXT TYPE /SAPCND/T_TST_ATTRIB_VALUE_EXT TTYP
at position 7.d) WORKING_SET_EXT TYPE DATA REF
at position 9.e) OVERLAP_ITEM_EXT TYPE DATA REF
at position 11.f) KOPOS_ITEM TYPE DATA REF
at position 12.g) LOCK_ITEM TYPE DATA REF
at position 13.h) SCALE_WORKING_SET TYPE DATA REF
at position 14.i) SCALE_WORKING_SET_EXT TYPE DATA REF
at position 15.8. Regenerate the following badi definitions:a) /sapcnd/tst_unit_usgb) /sapcnd/tst_appl_fld
Procedure to regenerate badi definitions:c) Transaction – se18d) Select the radio button Badi Name and give the badi name.e) Click ‘Change’ button.f) Click ‘Utilities’ menu button.g) In the ‘Utilities’ sub menu click ‘Regeneration’.9. Add the following self explanatory messages to the message class /SAPCND/MASTERDATA:a) 017 Condition record created by API not present in database for &1 &2 &3.b) 025 Overlap functionality cannot be tested due to error in condition record.c) 026 Scale table &1 is not initial for application &2 usage &3 for scale dim 0d) 027 Scale table &1 is initial for application &2 usage &3 for scale dim > 0.e) 028 Record values mismatch between API and database for scales field.f) 029 Mismatch between the API and DB in &1 table.g) 032 Condition maintenance not rejected even though KOPOS is greater than 1.h) 033 Condition record was selected in change mode even though KOPOS > 1.i) 040 Creation of condition record with scales failed for application &1.j) 053 Scales tables are initial for a condition record which has scales.k) 054 Maintenance mode is &1, where &2 is expected.l) 056 Dbaction value is not set to ‘U’ during update.m) 058 Unable to create working set handles for application &1 during setup.n) 060 No record was selected for lock verification (sceanrio &1).o) 062 Unable to carry out &1 test for application &2 (group &3).p) 101 Lock is not present as expected (&1, &2, &3).q) 102 Lock is erroneously present (&1, &2, &3).10. Add the following text symbols to the class /SAPCND/CL_MASTERDATA_UNIT_SRVa) 001 online partb) 002 update partc) 003 semantic keyd) 004 varnumh keye) 005 Create 1st record w/o savef) 006 Create 2nd record w/o saveg) 008 Create one record with saveh) 009 Direct change of saved recordi) 010 Select saved record in change modej) 011 Select in read mode and modifyk) 013 Select saved record in excl. change model) 014 Delete from change modem) 015 Delete from display moden) 016 Direct Delete w/o selecto) 017 Enqueuep) 018 ‘KOPOS’q) 019 Validity Period Overlap