Test Report /SAPCND/TST_MASTERDATA_UNIT

[] [] [] []

Symptom
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. [...]

wrong base value for external data source based condition

[] [] [] [] [] [] []

Symptom
You are using external data source based condition in your pricing procedure. Rate and base values for this condition is set using PRC_DATA_SOURCES BAdi implementation. You have created a transaction document (example sales order) based on this and saved that. Afterwards when you opened this document and made some pricing relevant [...]

Wrong value of group conditions during copy/customer return

[] [] [] [] [] [] [] [] [] []

Symptom
The value of a fixed amount group condition, e.g. freight, is wrong in a customer return.
Other terms
Group condition, customer return, copy, proportionated value, fixed amount, header condition.
Reason and Prerequisites
During exact copy, there shouldn’t be calculation happenning at the target document. The group conditon is recalculated in the return, although it should be fixed via [...]

Lock entries created even for non maintainable records

[] [] [] [] [] [] [] [] []

Symptom
Lock entries created even for those records of table /sapcnd/condindx which are not maintainable in CRM system(e.g. R/3 records whose maintenance not shifted to CRM).
Other terms
Condition Technique, GCM, /sapcnd/condindx, lock entries
Reason and Prerequisites
Program error.
Solution
Please apply the attached correction instructions.

Condition record maintainance problem -Exemption Certificate

[] [] [] [] [] [] [] [] []

Symptom
Go to transaction : TTEC_COND
Now select any country and now click on the Exemption Button. Now select the condition table SAPX0107 try to insert record.
Following problem faced by user:-
a)When creating a new record,not able to select a reason code ID from the lookup-list. [...]

WrongMsg:Condition cannot be processed manually

[] [] [] [] [] [] [] [] [] []

Symptom
1. The condition type customizing of the condition allows the manual processing of the condition.
2. The condition type customizing of the condition does not allow the change of the calculation type.
But when we edit the calculation type for the condition in the business document, a wrong message is raised i.e. “Condition cannot be processed [...]

DB index ‘DET’ for condition tables not always correct

[] [] [] [] [] []

Symptom
The DB index ‘DET’ for condition tables is not always correct.
This endangers the downtime of the upgrade to FP 20 since a wrong index creation can result in expensive drop and create index operation at the DB.
Other terms
Condition technique
Reason and Prerequisites
Program error during index generation
Solution
Program correction

Improving error handling in /SAPCND/TRN_BEFORE_EXPORT_R_OW

[] [] [] [] [] [] [] []

Symptom
Missing error handling in case result = 4(missing authorizations to display condition records)
Other terms
Condition Technique, /SAPCND/TRN_BEFORE_EXPORT_R_OW, Transport
Reason and Prerequisites
Program Error
Error handling is done only for the following two cases:
1. All selected condition records are in the condition maintenance buffer according to the maintenance mode(result = 0)
2. Lock could not be set in the maintenance mode(result [...]

ByD_HF: Error creating condition records (lock problem)

[] [] [] [] [] []

Symptom
Error message “Error while creating condition records: Locking object not possible” when calling the report RTTE_TAXRATES_SYNC which is accessing the tables /SAPCND/CONDINDX and /SAPCND/MNT_ENQUEUE_ARG.
Other terms
Lock issues, condition records
Lock problem is caused by usage of the transactional pattern “Save & Continue” instead of “Save & Exit”.
Valid for FP2.0 SP0.
Solution
Please note that this is [...]