Error in Specification import

[nirajsikligar]

Hello all,

I am trying to import specifications from one SAP system to other SAP system using import / export function.

I am able to generate .dat file for specifications from source SAP system and download to application server of the same system and then sucessfully upload in the target SAP system.

When I am doing import of the file in target system, getting following errors:

Could not locate any correct identifiers

Error searching for specification with key 000000129684 in system

Have created the specification headers in the target system same as source system with all the identifiers assigned before importing specification file.

Can anyone explain me how to resolve this error? Is there anything I am missing?

I have  Unicode system, so using the Character Standard as UTF-8.

Regards,

Niraj

[christoph_bergemann · Accepted solution]

Dear Niraj

First impression: no problem with upload of import file to target system and no problem with character font and both sap sysfems use e.g. UNIX as operating system

Can you answer these questions please:

1.) how many specications are part of your import file? only this one 000000129684?

2.) how many identifiers are part of the import file? Do you use a identification listing in the import to identify the correct specification? Which identifier do you use to match/find the correct specificaiotn in target system?

3.) which input criterias you have used during import?

I "struggeling" with your error message:

"Could not locate any correct identifiers" ; the dat file is "ASCII" oriented. Can you check the content of the file (refer e.g. to: http://help.sap.com/erp2005_ehp_06/helpdata/en/a7/287b420a6c11d28a220000e829fbbd/content.htm

regarding a example of a dat file)

If you have done  this correct:

Have created the specification headers in the target system same as source system with all the identifiers assigned before importing specification file.

Normally you try to perform the "import" by using the identifers as "matching criteria"; as long as customizing set up regarding identifiers (etc.) of target system is the same as source system normally the specification should be identified using an identifier (refer e.g. to: http://help.sap.com/erp2005_ehp_06/helpdata/en/a7/287bc90a6c11d28a220000e829fbbd/content.htm=

Please refer especially to this section:

"You can search using the specification key or using precisely defined identifiers. You can also enter combinations.

When searching using identifiers, the identification listing specified is used for the search. The position and priority of an identifier within an identification listing has... "

Regading your second topic

"Error searching for specification with key 000000129684 in system"

In most cases number schema of source system is different than target system; even if you use "numeric" values (running integer numbers as in your case)  the "last" number used in target ist different to source; assumption: you have used the "wrong" import parameter; it is quite tricky to have a number in source system like:  000000129684 and the same number in target system meaning really the same spec (there are procedures to make this happen).

PS: what is the business need of your import? why did you first created the specs in target system and why didn't you use the import to create the specs?

PPS: ALE is a further suitable option to distribute specifications and there data; regarding higher SAP releases you need to know that import/export can not help always; (some EH&S fields are not supported in inport/export; please refer to DG part of SAP EH&S documentation)

C.B.

[christoph_bergemann · Accepted solution]

Dear Niraj

can you check please if OSS note 1317589 is implemented? This note describes to a certain extent may be your import "problem"? (it is an old one dating from 2009; i found no really other useful OSS notes regarding your topic)

C.B.

[nirajsikligar · Accepted solution]

Hello Christoph,

Thanks for your elaborate answer.

Answers to your questions:

1.) how many specications are part of your import file? only this one 000000129684?

There are approx. 1000 specifications to be imported. Was trying to import only one as of now.

To add, this specification is used as a reference specification in source system and require the same in target system as well.

2.) how many identifiers are part of the import file? Do you use a identification listing in the import to identify the correct specification? Which identifier do you use to match/find the correct specificaiotn in target system?

There are 9 Identifiers assigned to this specification in both source and target system. Can you please help me with the information on how to use identification listing during import to identify correct specification? I did not use any identifier to match / find the correct specificaton in target system.

3.) which input criterias you have used during import?

Following input parameters used during export of specification in source system:

Exchange Profile: Standard

Check boxes marked for Usages, Assessment, Regulatory list assignments.

Answer to the question of creating specification header with identifiers in the target system is, when I first tried importing the specification I got the same error as:

Could not locate any correct identifiers

Error searching for specification with key 000000129684 in system

So thought that target system requires specification headers with identifiers to be created. So I created the same in target system and tried importing again. But got the same error.

Will check the SAP OSS message no. mentioned by you and implement the same if applicable to my system and update this thread.

Regards,

Niraj

[nirajsikligar · Accepted solution]

Hello Christoph,

Have checked the SAP OSS message as suggested by you and it worked for me.

As per the SAP message, I changed the value of field Search spec. type to 1 (search via specification key) from 2 (search via identifiers) in parameters tab in CG33. But I still do not understand why it takes 2 as default value even though when I did not searched specifications using identifiers during export.

But thanks a lot for suggesting right solution for me. Really appreciate as I am seriously running out of time and needed this solution immediately.

Regards,

Niraj

[christoph_bergemann · Accepted solution]

Dear Niraj

even taking into account the fact that you found a solution may be I can provide further tips and hints in import/export:

1.) it is a very good idea to use as a starting point only one specification key to be exported and then imported

2.) as mentioned in different threads in this FORUM: by using an "import" you can:

a.) create new specs

b.) update them (several subprocesses available; which may be are not easy to understand)

Depending on your choice a.) or b.) the process/Procedure is a "little" bit different

In most cases there is not the need ot export one spec from one system and then to import it to the other one as in most cases ALE is much easier to use.

Import is done / used mainly if you

a.) prepare EH&S data up based on content of an old legacy system

b.) or because of the fact that your company has acquired a different one having as well EH&S

Now: during the "creation of the new specs" you can first prepare identifiers (either by "hand" or by using the IMPORT process); Reason is "easy": in principle you can start with maintenance activities direct (e.g. assign material numbers etc.);

Now coming to the "update": after generating the spec you need in most cases time to "review" old system etc.; after that you perform the import using an export; this can be done step by step. Therefore you can use in source system a strategy only to export one property and then to import the same in target. Therefore there might be the need to prepare many properties trees in source and target system but the process is stable and you do the export/import step by step

Here now it is possible to perform an real update. E.g. you have generated a LIST_SUB with CAS NUM 50-00-0;  and you have prepared the export file.

Now if you have only one ! suitable specification in target system you can perform an "update" on the spec by using import if you have only prepared the CAS number on header level (there is a "but" but go on with reading)

Now depending on your import parameter you can use the "NUM CAS" in the import file to find the "right" spec" in target system; please refer to SAP Online help. The process is explained there quite good and after some "experince" in using it is a clever method to move data;

The import is the complexer process than the export.

Coming back to identification listing: you have exported roughly 9 identifiers per spec; let us assume:

NUM; CAS

NUM; EG

NAM SYN

etc.

Now by using a "identification listing in the import process you can "steer" the process. E.g.

If you have the situation that in your source system not all specs do have a "NUM, CAS" but a "NAM SYn" you can go on with import using a "identification listing" in target system like this:

First identify target spec using NUM, CAS, then, NUM, EG, then, NAM EG etc.

It is "critical" to understand teh difference in using "or" and "And" options during the import. Especially if you use identifiers as matching criteria.

Regarding

3.) which input criterias you have used during import?

Following input parameters used during export of specification in source system:

Exchange Profile: Standard

Check boxes marked for Usages, Assessment, Regulatory list assignments.

The "criticial" input is "how is the import done" (please refer to SAP online and how the system identifies the spec ("and" or "or" algorithm")

Important is this part of SAP docu:

You use the Spec. deletion type field to specify whether:

All specification data is to be deleted before import into the SAP system

·  No specification data is to be deleted and the import is to be carried out additively

·  Only the data that corresponds to the data origin and the data provider in the transfer file is to be deleted and reloaded

·  The value assignments of the value assignment types in the property tree specified as the parameter are to be deleted

·  Identifiers, references, and material assignments are not deleted

·  The specification data is deleted using change numbers

etc.

Congratulation that you found a solution; import is not an easy process

C.B.

[nirajsikligar · Accepted solution]

Hello Christoph,

Thanks a lot for your insight. Very useful information.

Indeed import process is a comple one. I had to use it as I am not very familiar with ALE process and was running out of time to deliver the solution.

Regards,

Niraj