Skip to Content
avatar image
Former Member

Error in Specification import

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

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Sep 24, 2012 at 05:41 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Christoph Bergemann

      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