Error : Message Class KI / No. 280

Account requires an assignment to a CO object ( Message Class KI / No. 280)

Message no. BEA766

Diagnosis

The message is not defined in the system. This means it is not possible to display the original long text for this message.

If the short text available is not sufficient, the long text for the message can be displayed in the R/3 OLTP System in transaction "Message Maintenance: E Initial Screen" (Transaction SE91). The message class and message number for the originial message can be taken from the short text.

Solution

Apply note 356094

AS per note solution:-

This note describes a modification solution which allows to transform message KI280 into a message that can be set. After you implemented the attached corrections, you can now change error message KI280 into a warning message, an I message or an S message using Transaction OBA5.
There are two control constants available in program SAPLKAIP:

• GD_VORGN_KI280_CUST
  This constant contains a list of business transactions for which KI280 is an adjustable message. In the standard setting, GD_VORGN_KI280_CUST has the value 'SD00/..../..../..../..../', that means, the system interprets the Customizing setting for KI280 in OBA5 only for business transaction SD00 (SD billing document). For all other business transactions, the system always sends the message as an error message.
  If necessary, you can supplement business transactionlist GD_VORGN_KI280_CUST with additional business transactions for which KI280 should also be adjustable. For example, you can change the value for GD_VORGN_KI280_CUST as follows: 'SD00/PMS1/PMSD/..../..../'. In this case, the setting in OBA5 is taken into account for business transactions SD00, PMS1 (Goods receipts) and PMSD (Stock transfer).
  You can find an overview of all business transactions via Transaction BS33 in the OK code field.

• GD_KI280_ALWAYS_CUST
  Using this switch, you can set the Customizing setting for message KI280 for all business transactions. You can activate the setting with an 'X'. The system does not consider the list of business transactions in GD_VORGN_KI280_CUST.

Caution
The change of message KI280 is a modification and is the customer's responsibility! If the modification produced unintentional data inconsistencies in CO, a repair by SAP Support will be charged!
When you import Support Packages, the modified programs may be overwritten by the standard programs. In this case, the modification should be implemented again.

Important for manual implementation of this note:

1. You must create the Include programs LKAIPF4R und LKAIPTDE.

2. So that message KI280 is adjustable using OBA5, additionally maintain table T100S using Transaction SM31. Insert the following entry:

Application area     MsgNo    Allowed     Standard
KI                  280      SIWE        E

Identify dependencies between Data migration objects

Soon after data migration objects are identified from each module, all the team leads should finalize the sequence in which data should be migrated. This activity is important from data upload perspective. For example system will not be able to identify tax upload data to certain account unless general ledger is uploaded into the system or while uploading customer master system will not allow uploading company code data unless reconciliation account is uploaded. To start with there will be two categories of data

• Primary Data

• Secondary data  

The primary data represents main data which does not have dependency on any other data. The only dependencies for these data are the configuration data ie; the field values. For example, primary data can be Material Master, Vendor master etc. The configuration data dependencies can be for example Customer specific Base unit of measure, Plants etc.

The secondary data are the data which use primary data, the examples of such secondary data can be Purchasing Info record which is build on Material master and Vendor master which are the primary data.

Similarly there will be cross modular dependency and such dependency should be identified in the initial stage and while designing the Data migration plan, this dependency should be considered. Sample sequencing of data migration objects can be:

SEQUENCE	DATA TYPES	MODULES	PREDECESSOR
1	CO-PA Configuration	FI/CO
2	G/L Accounts	FI/CO
3	Cost Elements	FI/CO
4	Profit Centers	FI/CO
5	Cost Centers	FI/CO
6	Tax & Bank Master Data	FI/CO
7	Special Ledger	FI/CO
8	Activities	FI/CO
9	Cost Objects	FI/CO	CO-PA Configuration
10	Work Centres	PP & QM	Cost Centres
11	QM Master Data (Sampling Procedure)	QM
12	QM Master Data (Catalog sets)	QM
13	Customers Master Data	SD
14	Storage Bins	MM
15	Quality Master Data (Characteristics)	QM
16	Quality Master Data (Classes)	QM
17	Quality Master Data (Inspection methods)	QM
18	Quality Master Data (Master Inspection characteristics)	QM
19	Materials (All material types)	MM
20	Quality Master Data (Assign Classes to Materials)	QM
21	Quality Master Data ( Material Specifications)	QM
22	Quality Master Data ( Inspection Plans)	QM
23	Quality Master Data ( Certificate Profiles)	QM
24	Bill of Materials	PP
25	Rate Routings	PP
26	Load Vendors Master Data	MM/FI
27	Quality Information Records	QM
28	Enter user master data	HR
29	Credit Management Information	SD
30	Standard Cost Calculation	FI/CO
31	Inventory Levels	MM/FI
32	A/P Invoices	FI/CO
33	A/R Invoices	FI/CO
34	Open Sales Orders	SD
35	Open Purchase Orders / Contracts	MM
36	G/L Balances	FI/CO