Report import - Dok-X

[nirajsikligar]

Hi,

Was trying to import report through tcode: cg3z / cg36 .

Getting following error:

Assigning values to characteristics to from class SAP_EHS_IBD_SDS failed.

Writing additional data from key file *.pdf.key failed

Have checked the class : SAP_EHS_IBD_SDS, it is with class type 017. Is it correct?

File being imported are in PDF format.

Key files used to upload and import is having extension *.pdf.key and transfer format used is BIN.

What could be wrong with import process?

Thanks in advance.

Regards,

Niraj

[christoph_bergemann]

Hello all

a.) first: please refer to this entry too:

b.) second: may be access rights are missing in the upload process

c.) third: I believe the pdf must be uploaded as BIN and the key file as ASCII

d.) fourth: The SAP class SAP_EHS_IBD_SDS is correct. PLease verify the number of characteristics too

e.) the key file should be of type "#######.key"" and not "####.pdf.key"

With best regards

C.B.

PS: normally one use a specific folder to store the pdf and key file to do the upload and not the folder you have used (matter additionally of read access to the files in the folder !)

Edited by: Christoph Bergemann on Mar 19, 2010 12:13 PM

Edited by: Christoph Bergemann on Mar 19, 2010 12:14 PM

Edited by: Christoph Bergemann on Mar 19, 2010 12:16 PM

Edited by: Christoph Bergemann on Mar 19, 2010 12:17 PM

[nirajsikligar]

Hi Christoph,

What exactly we mean by verify the number of characteristics ?

Regards,

Niraj

[christoph_bergemann]

Hello Niraj

linked to class SAP_EHS_IBD_SDS there should be a number of characteristics (material number, material name etc.). These characteristics will contain later the data from key file (not all of the data but some of them).

May be this link can help to:

http://help.sap.com/saphelp_45b/helpdata/en/35/6f28c1268b2239e10000009b38f984/content.htm

The class SAP_EHS_IBD_SDS belongs to class categroy 017 (document management) and not to 100 (EH&S value assignments)

Later on if you click with the mouse on the "Info" button in the report information system you should be able to see the content of the characteristics.

Hope that this helps.

C.B.

PS: this link is nice to: http://help.sap.com/printdocu/core/Print46c/en/Data/htm/english.htm

Here you will get pdf files (SAP 4.6c) regarding EH&S too and most important an example of a key file. This is very useful to find quick some answers (but is valid only until EH&S version 2.5 and not providing informations of higher versions).

Example of a key file:

Explanation

CPN=DUPONT

Company name

DTY=SDB

Document type (MSDS for Dok-X import)

PRN=LITHIUM POLYSILICATE

Product name

EDN=00001513

CTY=GB

Country

LAC=E

Language code

etc.

Edited by: Christoph Bergemann on Mar 19, 2010 6:28 PM

[nirajsikligar]

Hi Christoph,

b.) second: may be access rights are missing in the upload process

Checked, no access issue. files are getting uploaded through cg3z

c.) third: I believe the pdf must be uploaded as BIN and the key file as ASCII

Tried with pdf as BIN and key files with ASCII codes. no success.

e.) the key file should be of type "#######.key"" and not "####.pdf.key"

tried with key file with extension *.key but still same error.

You have mentioned that for Key file should include DTY=SDB

I have checked my DMS and could not find document type SDB. Have checked other IDES systelms also, but could not find document type SDB there. Do we need to create it? I have searched for some notes on this, but none of the notes states that there is document type SDB required in DMS.

Is there anything to do with path of directory?

Very useful links.

Thanks in advance.

Regards,

Niraj

Edited by: Niraj Sikligar on Mar 20, 2010 12:36 PM

[christoph_bergemann]

Hello Niraj

a.) DTY=SDB in key file => this is a little bit "surprising". If you check both function modules you will realize that in reality this information is not used "directly" but must be simply "there". So in principle no further DMS customizing etc. activity must be done

If this information is not in the file you can not import the pdf/key files. (by standard SAP is delivering document type IBD which should be used regarding imported reports).

Most important is the "Country" and "Language" information in the key file. Using the condition tables 4 (which are used in report distribution process and define how the "correct" generation variant is selected) (together with the user exit as prepared in customizing) the system is doing this (check http://help.sap.com/saphelp_45b/helpdata/en/35/6f28c1268b2239e10000009b38f984/content.htm; Report import: check additional settings; the topic is explained clearly in my opinion).:

1.) The country is used to find the correct generation variant (you must have prepared a corresponding report category)

2.) the language will be the language of the report

This process to upload/import the pdf/key files is not so "logic" in my opinion but it does work.

Using the customizing (proper user exit definition) the system "knows" which reprt type the new report belongs. Using this informaiton to gether with the country information in the file the system tries to find the correct generation variant

e.g. report category IBD_MSDS together with country DE would lead to report generatio variant e.g. IBD_DE.

This generation variant needs to be "there". Here may be some trouble could happen too.

b.) the generation variant must be defined without ! a report template but should have assigned SUBMASTER and MATMASTER as well it must have one validity area; one rating etc. If you define this generation variant "wrong" you will get problemes later in handling these "imported" reports. Keep your eyes on that.

b.) You need not only SAP rights but you need read right on the folder there you have put the files. Please try transaction "Al11". Using this SAP transaction you should be able to take a look on the folder structure of the application server (there normally key and pdf files are stored). If you can "see" the files you have the right access rights

Your original error message:

"Assigning values to characteristics to from class SAP_EHS_IBD_SDS failed.

"Writing additional data from key file *.pdf.key failed"

could indicate that there is a problem here.

The error you have reported could relate to problems with the 017 class. Please verify that using transaction su53. You need write access to classes of type 017 in your SAP authorization so that the key file content can be uploaded and stored in the characteristics.

In any case: try the debugger to get an idea there the problem is located.

Depending on your OS: E.g. take care in "naming" of directory and file. Both are case sensitive in UNIX

Normally you will have structure like:

"/directory/transfer/...."

Any file of type ".key" and "pdf" located in this folder is "imported" in one step (and I believe deleted after the import was successful; please check).

By the way: is the preimport check sucessful (you can check there potential problems too and you will get a small log indicating potential problems)?

I hope that you will be able to remove the problem.

With best regards

C.B.

Edited by: Christoph Bergemann on Mar 20, 2010 4:08 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:09 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:21 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:23 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:26 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:26 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:27 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:28 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:29 PM

Edited by: Christoph Bergemann on Mar 20, 2010 4:29 PM

[nirajsikligar]

Hi Christoph,

Very useful information. wll get back once the issue is resolved.

Due to some problem not able to assign you the points...

Thanks and Regards,

Niraj

[nirajsikligar]

hi Christoph,

I did all the settings as mentioned in the iMG activity: Report Import: Check Additional Settings.

In cg 3z tcode I could able to transfer the files from my desktop to the directory, but when I use tcode cg36 to import files from directory, after assigning the path, I clicked on Check directory button, nothing happened on my front end. Then I clicked on import button, I get message: Execute the function 'check directory' first.

When I cheked in su53 for authorization subobject IMP-REP was missing in object EHDI.

After getting authorization, when again tried, got same error. Again authorization checked it was giving authorization failed for tcode PFCG. But even after getting authorization for PFCG tcode, gettting same message and same authorization failed error of tcode: pfcg.

I tried the same thing on other server, there authorization check was sucessful, no authorization failure here, but still that message is appearing for this server also : Execute the function 'check directory' first.

Anything wrong with Preimport check?

Any idea? is there any other authorization which is missing?

Regards,

Niraj

Edited by: Niraj Sikligar on Mar 25, 2010 1:45 PM

[christoph_bergemann]

Hello Niraj

I am a little bit "surprised". T code PFCG belongs to the "profile generater" (e.g. take alook here http://publib.boulder.ibm.com/tividd/td/ITWS/SC32-1278-00/en_US/HTML/TWSAPPEX115.htm).

In any case: a number of further access problems (indirect sorry) could be a "reason".

To give you only some ideas there you could/should look at:

the result of the inbound process should be a report assigned to a specification in some status. A number of access rights must be granted to get such a "report" e.g. imported in status "ready" or so.

1.) The generation variant you are using contains a "report category" and "ratings" as well as validity area(s). You must have write access here or the report will not be imported => the correct defintion of the generation variant is a "critical" factor not only to get the report imported but to handle the documents later in the system (hint. the "set historic" checkbox)

2.) Further more you must have the rights to change "status of the report". May be as you know there is a status net in report releasing. This access right is linked as far as I can remember to (the report category ?) and report type (IBD !!). Here you must have rights regarding all status (e.g. W7 (released)).

3.) I am not sure about but please check that you have enough access rights regarding the specification there you would like to import the report (most important: write access to the substance authorizationgroup).

The link http://help.sap.com/saphelp_45b/helpdata/en/35/6f28c1268b2239e10000009b38f984/content.htm

is only giving you an idea how you could use this function. This is a good starting point. In reality you need different generation variants, report category etc. and therefore you should not use this example on a long term view.

The "check directory" is a mandatory step as explained in the link:

"Pre-import serves as a file check that you must carry out in your application before executing the actual import.

The function module for this is C13G_DOKX_SDB_PREIMP."

This function is clearly not an "enduser function". Therefore some further basic SAP access rights might be missing too.

In any case: use the debugger to get further ideas there the system "hinders" you. MIght take some time but at the end hopefully all problems can be removed.

May be this helps.

With best regards

PS: the actual link is: http://help.sap.com/erp2005_ehp_04/helpdata/en/c1/eda0f591ec12408b25e7a1b369ca45/frameset.htm

Take a look here " Report Import: Process" and here " Importing Dok-X MSDS Reports "

Most important are the parameters:

DTY

CTY

LAC

FNA

FFF

A further parameter is providing ("normally") the specification key. PLease check function module. Any potential paramter is mentioned in the function module.

Edited by: Christoph Bergemann on Mar 26, 2010 9:57 AM

[nirajsikligar]

Hi Christoph,

Thanks for thereply.

I was doing exactly the same as mentioned in the link. But I am failing in the first step of Check Directory fucntion.

During debugging I could find that system is not finding *.key file from the directory.

Still in the process of debugging.

Do share if you have any clue about why system is not able to find the file from the directory.

Regards,

Niraj

[christoph_bergemann]

Hello Niraj

actually no further idea from my side (sorry). May be takle a look here too:

or here

(not the same topic but similar).

Did you check t code al11 and you can see the file as requested? If so the re imp check should really run (if the directory used is typed in correctly).

This Doc X interface (or this report import process) is quite old in EH&S. I have no knowledge regarding recent OSS.

With best regards

C.B.

[nirajsikligar]

Hi Christoph,

Thanks for all replies. They were really valuable inputs.

I am trying to debug it and will update if I get any solution.

Regarding AL11 authorization, I do not know how to see the files there, but I have SAP_ALL authorization, and in su53 I am not getting any authorization failure report.

Once again thanks for all your inputs.

Regards,

Niraj

[christoph_bergemann]

Hello NIraj

regarding AL11:

Using this transaction you can browse the folder structure of the application server. Normally key and pdf files are located here in a special folder.

Further on: take a look here:

I have found in addition some old OSS which might be helpful in the future: Note 1425569, Note 1408009, Note 1156981.

Hope that you will be able to detect the problem.

With best regards

C.B.

PS: May be take a look in addition to this really old OSS: Note 153233

PPS: May be check this thread in addition:

Edited by: Christoph Bergemann on Mar 26, 2010 6:45 PM

Edited by: Christoph Bergemann on Apr 3, 2010 3:50 PM

[christoph_bergemann]

Hello Niraj

there are now a high number of similar threads available in this FORUM asking questions regarding this topic. Here is the list (which is hopefullly complete). Some of them could be a help to on with your issue.

With best regards

C.B.

PS: AL11: during the upload propcess you must specify a floder in UNIX or Windows there the files shoule be located. Using AL11 you can controll if they are "there" etc.

Edited by: Christoph Bergemann on Apr 10, 2010 6:14 PM

[nirajsikligar]

Hello Christoph,

Was trying the same scenario again with key file with data as :

SID=300001004822

LAC=E

CTY=US

FNA=4822E.pdf

FFT=PDF

PRN=AEROTECH 1570

DTY=SDB

DAT=22.06.2009

VER=1.0

I have checked the Schema Table 4, where the Generation variant is mentioned, which has validity area as Region_NA.

Also as we are on Windows system, there is ZWWI_GET_DIR created and mentioned in the respective Environmental parameter.

I tried uploading Key file as *.key and selecting ASC as transfer format but no sucess.

Have checked the authorization also. There is no authorization error.

Log file shows error as :

Cannot open the file.

Any help?

Regards,

Niraj

[nirajsikligar]

Hi,

Issue resolved.

Problem was, there were some report key files earlier uploaded with missing data. The previously uploaded key files deleted from the application server and corrected data uploaded again. Then successfully imported.

Thanks all for the extended help.

Regards,

Niraj

[former_member214272]

Hi

We are facing the same error

"Cannot open file
sapehpi\sapmnt\interface\erp\in\ehs\data01.p ()"

System is not update file , the system terminated processing.

For more details please ref. Niraj Posting

Thanks

Sunil