Error Elimination

Main Menu

Picture 1.

The Menus to focus in LDW are Error handling which is highlighted below:

1) Maintenance LDW tables

This is the menu where you as local administrator have to maintain the link between Sales
Rep in Siebel/COH and LDW/SDW, Sales Channel and Sales region structure. It is also the
menu where you define what Operational Units to load into the LDW and which of the local
cubes (if there are more than one) that the unit should be included in.

2) Error handling

This is the menu where you have to monitor and take action on errors in the data. This is
one of the most important menus for the local administrator. And you should maintain it
daily.

3) Operational Procedures

This menu should not be used unless you are instructed to.

4) PS recalculation

This menu should not be used unless you are instructed to.

5) Other functions

1
 This menu should not be used unless you are instructed to.

6) Data loading

This menu should not be used unless you are instructed to.

7) Communications

This menu should not be used unless you are instructed to.

2
Error handling

This menu gives you the possibility to check, and correct errors related to data sent to LDW.
The menus we will focus on in this section is: 1.

Picture 2.

Picture 3.

3
All errors will not be covered in this document, most errors are self-explanatory and can easily sent to
LDW from the source system ’COH’. In this document we cover only those errors that require some
actions to be taken to correct the errors.

If the Error is for below files, please follow the instructions as given below:

ID File Error Instructions

Code

1 Customer Grouping 512 Please transfer the Incident to SDW Team (or) contact Robert
Lorentzon ([email protected])

Make change in COH

For most kinds of errors it is possible to correct the error in COH. Each time a record is
changed, a transaction for the Data Warehouse is created. If there already is a record with
the same id in the Extended file (= the record in error), this record will be updated with (=
replaced by) the new transaction.
If the record in error does not come from COH but from another system (a local connection
has been implemented), the same rules apply, provided your local implementation also
updates (replaces) the record in the Extended file.

Make change in source-system to COH

Errors regarding Customer schedule that cannot be related to customers or products shall
be corrected in the source-system to COH.

Enter missing customer or product

If a new customer or product has been stopped by the validation, subsequent
errors may occur in order line, invoice line, customer's own designation or
customer schedule records. For example: If a new customer transaction is
stopped by the validation, also all order lines referring to this customer are
stopped. If you eliminate the customer record error, the order line error will also
vanish and the order line is entered into LDW database.

Reloading data
At rare occasions errors can be eliminated by reloading data from COH (and other source
systems). One example can be when you have updated your source system files by "fix"
programs, where no transactions to the Data Warehouse have been created. Before
performing any data reloading, please contact the Central Support Team for instructions.

4
Customer Errors

Most customer record errors shall be corrected in COH (and other customer source systems,
if any).
If the Customer data is correct in COH and not correct in LDW, for most time reloading of
customers from COH to LDW will solve the issue. We can reload only the customer in error to
LDW as well.
Below you can find explanations and advice for some errors.

409 Customer already exists in LDW

You have received an "add" transaction, but there is a record in LDW Customer file with the
same id, but with a different short name.
Possible reasons and actions
 An old customer id has been reused for a new customer.
 Conflicting customer ids when customer data entered from more than one system.
Find out reason and take appropriate action.

410 Invalid industry code

The industry code in the customer record cannot be found in the LDW Industry code table.
This table is centrally defined and is per definition correct. Error 410 is also created by the
Validate customer/industry code relation function on LDW Other Functions Menu.
Actions
 Is the Industry code mentioned in Customer record valid? If not please correct the
error in the source system (COH or other).
 Do you have the latest version of LDW Industry code file? If not contact central
team for support on how to get the latest IC file into LDW.

411 Invalid operational unit code

The operational unit code in the customer record cannot be found in LDW Operational unit
file. Error 411 is also created by the Validate customer/operational unit relation function on
LDW Other Functions Menu.
Possible reasons and actions
 Your LDW Operational unit file is not correct or complete. Update your LDW
Operational unit file. And this can be done through the ‘Maintenance Window’
(Picture 1).
 The operational unit code in the customer record is erroneous. Enter a correct
operational unit in the customer in COH (or other source system).

412 Invalid sales representative

The sales representative code in the customer record does not exist in LDW Sales
representative file. Since LDW Sales representative file is updated with data from COH Sales
representative file, these files shall have the same data. The function Remove unused sales
representative which is found on the other Functions Menu, can, however, remove unused
records from the LDW Sales representative file. (An unused record is a record that is not
referred to from any record in LDW Customer file). If a removed unused sales representative
is linked to a customer in COH (or other source system), error 412 occurs.

5
 Actions
The missing sales representative entry has to be re-entered into LDW Sales
representative file. Make change(s) in COH Sales representative file (e.g. add a period
after the name + remove a period after the name), or use DFU (or any other file utility)
to enter the missing record.

413 Invalid sales region

The sales representative in LDW Sales representative file does not have a valid sales region
entry, i.e. the sales region field is either blank or has a value that does not exist in LDW
Sales region file.
Actions
If the sales region field is blank: Enter a valid sales region code into the LDW Sales
representative record. If the sales region field is not blank: Check if the field value is
correct. If not: Enter a valid value. If it is correct: Create a corresponding record in LDW
Sales region file.

414 Invalid Consolidated sales rep

The sales representative in LDW Sales representative file does not have a valid consolidated
sales rep entry, i.e. the consolidated sales rep field is either blank or has a value that does
not exist in LDW Consolidated sales rep file.
Actions
If the consolidate sales rep field is blank: Enter a valid consolidated sales rep code into
the LDW Sales representative record. If the consolidated sales rep field is not blank:
Check if the field value is correct. If not: Enter a valid value. If it is correct: Create a
corresponding record in LDW Consolidate sales rep file.

6
Customer Own Designation

The most common errors are 610 and 611 (see below). Other errors have to be corrected in
the source system.

610 Customer not found in LDW

The customer id in the customer's own designation record does not exist in LDW Customer
file. This customer record has probably been stopped by the validation.
Actions
If the customer record has been stopped by the validation: Eliminate the error of this
record so that it is entered into the LDW Customer file, and the error in the customer's
own designation record will disappear. If there is no erroneous customer record, check if
the customer exists in the source system. If it does, make a change (+ a re-change) in it
to create transaction(s) to LDW (or) use the “To LDW” option in COH.

611 Product not found in LDW

The product id in the customer's own designation record does not exist in LDW Product file.
This product record has probably been stopped by the validation.
Actions
If the product record has been stopped by the validation: Eliminate the error of this
record so that it is entered into the LDW Product file, and the error in the customer's own
designation record will disappear. If there is no erroneous product record, check if the
product exists in the source system. If it does, make a change (+ a re-change) in it to
create transaction(s) to LDW (or) use the “To LDW” option in COH.

7
Invoice Line Errors

Since it is impossible or difficult to recreate invoice lines, validation errors cannot be

eliminated by recreating invoice lines in the source system. Nor can invoice line change
records be processed by LDW. Fortunately, there are hardly ever any errors regarding
missing or erroneous field values in invoice lines received from COH, although marketing
period errors (124 and 125) may sometimes occur. Other errors that occasionally may occur
are 114, 116, 117 and 119 (see below).

114 Customer not found in LDW

The customer id in the invoice line record does not exist in LDW Customer file. This
customer record has probably been stopped by the validation.
Actions
No customer was found for the invoice transaction. And this can be due to the fact that
customer record has been stopped by the validation file. If the customer record has been
stopped by the validation: Pls look into the customer errors and eliminate the reason for
error of this record so that it is entered into the LDW Customer file, and the error in the
invoice line record will disappear. If there is no erroneous customer record, check if the
customer exists in the source system. If it does, make a change (+ a re-change) in it to
create transaction(s) to LDW (or) use the “To LDW” option in COH.

116 Charge key not found in LDW

8
The charge key of this invoice line does not exist in LDW Charge code file. The charge key
has probably been stopped by the validation.
Actions
Check in the error handling if the missing charge key is found there. If found, correct the
error. If not found there, check that the charge key exists in COH. If it does, create
transactions to LDW by changing the charge group + changing it back again.

117 Product not found in LDW

The product id in the invoice line record does not exist in LDW Product file. This product
record has probably been stopped by the validation.
Actions
If the product record has been stopped by the validation: Eliminate the reason for error
of this record so that it is entered into the LDW Product file, and the error in the invoice
line record will disappear. If there is no erroneous product record, check if the product
exists in the source system. If it does, make a change (+ a re-change) in it to create
transaction(s) to LDW (or) use the “To LDW” option in COH.

119 Invoice line already exists in LDW

There already exists a record in LDW Invoice line file or LDW Invoice line history file with the
same id (invoice number + invoice line + invoice date) as the invoice line record in the
extended file.
Possible reasons and actions
 An invoice number has been reused by the invoicing system. Should never happen!
 Duplicate transactions to LDW have been created. Delete the record in the
extended file (DFU or similar tool has to be used).

124 Marketing period < current month

125 Marketing period > current month
The quality responsible must study these errors to see whether the marketing period is
correct or not. If it is correct, the records shall be approved; otherwise the marketing period
shall be changed. Select option 2 Marketing period errors on the LDW Error Handling Menu
to display the records in error. In the Marketing period errors screen you can choose to
approve and correct the marketing period. Once the marketing period has been approved
for a number of records, it cannot be changed any more. You can, however, change the
marketing period more than once as long as you do not approve it.

9
Order Book Errors

Since a new order book is received from the source system in each LDW
Daily/Weekly/Monthly batch, all records in error (if any) in the extended file will be deleted
by the batch before the new order book is received. However, if the error has not been
corrected, the same error will occur again when the new order book is validated. Due to this,
the error date of an order book error is always the date of the latest validation, while error
date of other errors may be weeks or months old, if error handling and elimination have
been neglected.
Most order book errors have to be corrected in the source system. For errors 213, 215, 216
and 218 some advice is given below.

213 Product not found in LDW

The product id in the order book record does not exist in LDW Product file. This product
record has probably been stopped by the validation.
Actions
If the product record has been stopped by the validation: Eliminate the error of this

10
 record so that it is entered into the LDW Product file, and the error in the order book
record will disappear. If there is no erroneous product record, check if the product exists
in the source system. If it does, make a change (+ a re-change) in it to create
transaction(s) to LDW (or) use the “To LDW” option in COH.

215 Order line already exists in LDW

There already exists a record in LDW Order book (or LDW Invoiced order file) with the same
id (order id + order line + order split) as the order line record in the extended file.
Possible reasons and actions
 An order id has been reused by the order entry system. Should never happen!
 Duplicate transactions to LDW have been created. Delete the record in the
extended file (DFU or similar tool has to be used).

216 Customer not found in LDW

The customer id in the order book record does not exist in LDW Customer file. This customer
record has probably been stopped by the validation.
Actions
If the customer record has been stopped by the validation: Eliminate the error of this
record so that it is entered into the LDW Customer file, and the error in the order book
record will disappear. If there is no erroneous customer record, check if the customer
exists in the source system. If it does, make a change (+ a re-change) in it to create
transaction(s) to LDW (or) use the “To LDW” option in COH.

218 **Warning! Order book is missing!**

The Extended order file does not contain any order records. One record containing this error
has been created in the file.
Consequences
The order processing part of the LDW batch has been stopped. The LDW Order book file
contains the latest received order book, and this data is used as order book data in all
Power Cubes created by the latest LDW batch. This means that recently invoiced orders
may be included in a cube both as sales data and order book data.
Without an order book, no order intake data can be created. When (finally) a new order
book is received, all created order intake data will be given the selection date (order
book version date) of this order book as order intake date.
Unless properly action is taken (see below), order book versions will be missing in the
Order book follow-up (weekly and monthly).
Possible reasons
 No order book was sent from the source system.
 An order book was sent from the source system, but was not available when the
order processing part of the LDW batch was run. The reason may be bad timing
between the COH and LDW batches or that the LDW MONITOR NEP was not active.
Actions
Check if the order book can be found in DWFxx/OADW02 which is the interface file in
which the order book shall be when the LDW batch is started. If the order book is there
now: Start the LDW order batch (daily, weekly or monthly) from the Operational
procedures menu, option 70, 71 or 72.

If there is no order book in DWFxx/OADW02, then check DWXxx/OADW02. If the order

book is found there, check that the LDW subsystem DWSxx and the MONITOR NEP are
active (WRKSBSJOB DWSxx). When the MONITOR NEP is active, it will retrieve the order

11
 book from DWXxx/OADW02 and enter it into DWFxx/OADW02..

If there is no order book in DWXxx and DWFxx, then check SCFxx/OADW02 (DSPFD
SCFxx/OADW02). This file is most probably empty, but the "Last Change Date/Time" tells
you when the last order book was forwarded to the Local Data Warehouse. If no order
book is found in DWXxx/OADW02, and "Last Change Date/Time" contains the date and
time of the order book used in the previous successful LDW batch (where no error 218
exists), no order book has been created in the latest COH daily batch. Possible reasons
for this error are outside the scope of this documentation.

Create New orderbook in COH and resend.

The library list must contain your SCFxx library. When this order book has arrived to
DWFxx/OADW02, you can start the LDW order batch (daily, weekly or monthly) from the
Operational procedures menu, option (70, 71 or 72).

If the order book is missing in a weekly or monthly batch, it is strongly recommended to

try to re-run the LDW order batch with an order book available. Otherwise order book
versions will be missing in the Order book follow-up files.

Product Errors

Seven possible errors are checked by the validation function. Four of them hardly ever
occur, but the errors 506, 509 and 510 may occur now and then.

506 Current PS cost is missing

The validation of product transactions includes a test that PS cost 2 (= current PS cost) is
not equal to zero. If it is zero and the PARM05 record has value Y, also the Analysis value
field of the product transaction is checked. If the Analysis value is zero, error 506 "Current
PS cost is missing" is assigned to the record; otherwise the record is approved. If PS cost 2 is
zero and the PARM05 record is N, error 506 "Current PS cost is missing" is assigned to the
record.

An essential task for the Data Warehouse is to calculate and recalculate sales values in PS

12
for sales data. To perform these calculations, PS cost values for each sold product are
needed. Nearly all products have a PS cost, but there are also a small number of them that
do not have this cost. However, nearly all of these products without PS cost do have an
Analysis value, which is a value similar to the PS cost. If you want to, you can use the
analysis value instead of the missing PS cost for the LDW calculations and recalculations of
sales values in PS. In the LDW Parameter file, there is a record id PARM05 which is called
"Use Analysis value if PS cost is missing". There are two values for this parameter: Y (= Yes)
and N (= No). If the parameter value is Y, the analysis value will be used for PS
(re)calculations in case there is no PS cost in the product record in LDW Product file. If the
parameter value is N, analysis value will not be used for PS (re)calculations.

The processing rules for a product record where current PS cost is missing are described in
the table below.

Value of PARM05 record

Product record in Extended Product Y N
file
Has Analysis value No error Error 506
Analysis value missing Error 506 Error 506

Conclusions

If you know that the products are old without any sales in the period covered by your Data
Warehouse, and will never be used again for orders and invoices, you may temporarily set
the error code update flag = Y. We recommend you to run an extra validation + update, in
order to avoid letting into your LDW Product file new products without PS cost and analysis
value that you have not checked in the error handling.
Set Error code Update flag = Y (Only for Error Code: 506)
Each error code has an Update flag whose value is Y, N or blank.
 Value Y means that records with this error may be entered into LDW in spite of the
error.
 Value N means that records with this error cannot be entered into LDW.
 Value blank also means that records with this error cannot be entered into LDW.
 The difference between N and blank is that update flag N can be changed to Y, while
value blank cannot be changed at all.
 The default value of an error code is N or blank.
If you change the update flag of an error from N to Y, all records having this error will be
entered into the LDW database files. You should avoid using this way of eliminating errors,
but there may be rare occasions (Should be used only in case of error code 506, if the
product is old product and not used) when this method is appropriate. If you want to set the
error code update flag = Y, you should do like this:
1. Set the error code update flag = Y.
2. Run an extra validation (use LDW Data Loading Menu) in order to detect other errors that
have been "hidden" by the error whose update flag has been changed?
3. Update LDW database (use LDW Loading Menu).
4. Set the error code update flag = N, (unless you want it permanently set = Y).

13
509 PRUM conversion factor is missing
The PRUM conversion factor is used by LDW in several calculation. Therefore a product
without this factor must not be entered into LDW Product file. Correction shall be made in
the source system.

510 IPS code is missing

The IPS code is currently not used for any specific purpose by LDW, but these errors should,.
if possible, be corrected in the source system.

These errors are either errors in transactions from COH (301-309) or errors detected inside
LDW when performing updates or consistency checks (311-316). The most frequent errors
are 304, 306, 307 and 314.

Charge Errors
304 Charge group not found in LDW
The charge group in the charge record does not exist in the LDW Charge group file.
Possible reasons and actions
 Erroneous charge group used in COH. Change the charge group of this charge

14
 code in COH.
 If the charge group is 99 the marketing flag shall probably be N, but have been
set to Y in COH. If you change the marketing flag to N in COH, you probably need
to delete the record in error manually. Use DFU or similar tool. The record in error
is in the DWFxx/DWTRCC file.

306 Invalid charge group

The charge code in error is a centrally defined charge code. The charge group you have
entered in COH is not equal to the centrally defined charge group.
Actions
Check in LDW Service code (LDW Maintenance menu, option 17) what the correct charge
group is. Enter this charge group into the charge code in COH.

307 Invalid charge group for services

The charge in error is locally defined. Its charge type is S (service) and its charge group is
00. Charge codes with type S must not refer to charge group 00.
Actions
Change the charge group to a valid group or change the charge type. These changes
shall be made in COH.

314 Charge missing in charge code file

These errors are created by the Check charge code function, which checks that each charge
code in LDW sales database exists in LDW Charge code file. Error 314 means that you have
sales data referring to a charge code that is not defined in your LDW.
Actions
Check if the charge code is defined in your COH. If yes, its marketing flag is probably N.
If marketing flag N is correct, the sales data of this charge code ought to be removed
from your LDW database. Please, contact the LDW/MISS central support team for further
information. If the marketing flag shall be Y, just change it to Y in COH and the error will
disappear after the next LDW night batch.
If the charge code is not found in your COH, you have to find out (in one way or another)
whether the marketing flag of this charge code shall be Y or N. If it shall be Y, you must
enter the charge code into COH in order to create a transaction to LDW. If you do not
want this charge to be used, you can inactivate or delete it in COH afterwards. If the
marketing flag shall be N, the sales data of this charge code ought to be removed from
your LDW database. Please, contact the LDW/MISS central support team for further
information.

15
Customer Schedule Errors

Errors related to customer and product data can be corrected in COH or LDW. Other errors
should be corrected in COH. Below you can find explanations and advice for some errors.

430 Version date is missing

No version date has been entered by COH. The version date shall be the date when the file
to LDW was created in COH.

Actions
 Report this error to the COH helpdesk

431 Delivery year/month is missing

Delivery year/month is missing in the PLAN file in COH.

Actions
 Report this error to the COH helpdesk

432 Delivery year/month not valid

The delivery year/month field does not contain a correct value. It should look like 'YYYYMM'.
Actions
 Report this error to the COH helpdesk

437 Delivered quantity is missing

Quantity is missing in the PLAN file in COH.
Actions
 Report this error to the COH helpdesk

16