Create mass specifications and update value assignments

[Former Member]

Hello

I have a requirement to have multiple specifications created in my SAP EHS system and update specific value assignments for them.

If I have raw data provided to me in form of an excel spreadsheet, how can I create and update mass specifications. Please note that my client does not have a license for data editor/OCC.

The spcific tasks are:

- create multiple specifications

- assign inheritance relationships for each

- update specific properties (mainly physical and chemical properties) for each

- update composition values for each.

Appreciate any inputs.

Thanks.

Sachin

[christoph_bergemann · Accepted solution]

Dear Sachin

please don't mix topics. Data Editor is not supported any more; it is only available as a service from SAP; But OCC is supported and use of OCC is part of your EHS license. So you can use OCC. And clearly you can use OCC do "load something".

For OCC: please check this document: http://scn.sap.com/docs/DOC-59534

You will find find references to many OCC threads. For OCC: there is one quite important new OSS note describing OCC changes. OCC was redesigned so that you will now find nearly the same options in OCC like in DataEditor.

The story starts with your statement:

If I have raw data provided to me in form of an excel spreadsheet, how can I create and update mass specifications.

=> whatever tool etc. you will use one can be pretty sure that you need to transform your EXCEL to something different (either EXCEL ready for OCC or ..)

We should differentiate the "create" part from the "update" part.

in principle: you can use EHS standard import (inheritance is not possible) and you can use OCC (not sure about inheritance, we are not using OCC for load purposes)

Regarding:

- create multiple specifications => you can do via standard import

- assign inheritance relationships for each => not sure regarding OCC; to my knowlegde: not possiblel with "standard import"

- update specific properties (mainly physical and chemical properties) for each => you can use either "import" or OCC

- update composition values for each. => you can use either "import" or OCC

A different option (nether used it) is:

EXCEL data => XI/PI => SAP EHS

or

Use of LSMW via ALE

EXCEL => LSMW => ALE to EHS

For "creation" I am pretty sure that you can use that; for update: no idea: nether tried

C.B.

PS: you need to understand the "inheritance" option; tehn you will understand that it is not easy to "populate" this by "import".

ALE is one suitable way to do it. So as long as you can prepare suitable IDOC you can do an import

[Former Member · Accepted solution]

Dear Christopher

Thanks for your prompt and detailed response.

My situation is this.

For OCC:

If i understand correctly, I need to have OCC installed in my local system. And once the necessary configuration has been done, I can call OCC via a user exit from within the specification workbench.

In my case, I am accessing my client network remotely through citrix and do not have OCC installed on my system. Then it would mean I would need to access a client system (through remote desktop) that has OCC installed and then carry out the upload process.

For Standard Import:

Alternatively, I can use the standard import functionality to do the upload and update. For this, I need to convert the excel to a data file and then import using standard functionality? Which means most of the effort required would be to modify the excel file and map it to the relevant specification and value assignment tables.

Do correct me in case I have wrongly stated anything.

Thanks,

Sachin

P.S. As for inheritance, I will study in further detail to find out what the best approach could be.

[christoph_bergemann · Accepted solution]

Dear Sachin

This is what i know about "citrix":

On a client you have some software (the citrix client) installed calling a "citrix farm"; on the citrix farm a full installation is done like:

SAP GUI, WinWord... and anything else to really work with SAP EHSSAP ERP (to log on to SAP most simply). I have never ever tried to do an upload using OCC with such a kind of architecture. But my understanding would be:

Now you have three pieces of software installations, which work together.

1.) Your Citrix log on option on your client

2.) on Citrix farm the software to log on to SAP (as SAP Gui)

3.) and Citrix farm will then call/communicate with SAP; As for this you have on Citrix farm a WWI installation you can have in my opinion as well an OCC installation; But never tried it...

Regarding:

or Standard Import:

Alternatively, I can use the standard import functionality to do the upload and update. For this, I need to convert the excel to a data file and then import using standard functionality? Which means most of the effort required would be to modify the excel file and map it to the relevant specification and value assignment tables.

Here you are 100% correct. The most crucial (and not easy task) is to generate a "loadfile" according to SAP EHS standard import functionality using some data (e.g. in your case EXCEL based); this is the most time consuming step and you will only !!!! suceed if you have understood 100% perfect !!! the standard import and the load file structure. DON'T use thsi option if you have aNY KIND OF PROBLEM (in understanding the design etc.) WITH THIS INTERFACE......

If you read´the many threads regarding standard import: I would imagine that 80% of the consultants acting in EHS do not love (not to say hate) the file structure needed. One error in the file and you can not load! And there is no absolutely no error handling possible during the load; either the data is correct or not; if not: your database can get corrupted.!!!! ..as there is nearly no feasible approach to go back

This and the not "userfriendly" handling of standard import  (and you need high access rights on the top) is one additional reason they consultants love to use OCC: OCC is much simpler; especially if you read very carefully the new options using OCC.

Please check SAP marketplace and the new options with OCC:

C.B.

[Former Member · Accepted solution]

Dear Christopher.

Thanks.

Based on this I see that I have an option of either setting up OCC and use it or go with the difficult and tedious option of preparing load files to use the standard import functionality.

If I create mass specifications using the standard import, is there not an option available to have an ABAP program created to update the properties and composition?

Regards,

Sachin.

[christoph_bergemann · Accepted solution]

Dear Sachin

you have SAP standard options;and you have "ABAP". And yes you can use ABAP and functions as delivered in SAP EHS (BAPIs/APis) to

a.) create specifications

b.) do update

etc.

if you are willing to create blueprint/design and create ABAP lines of code just do it... (and check this very new document: )

SAP delivers some default ABAPs (example implementations) which explains the use of the BAPIs/APIs. PLease check this FORUM; they are discussed often; but at the end: you "redesign" from a certain aspect standard import or OCC approach

Check for reference to these threads (check the BAPI/API section)

If there is really the need to try something: then may be try to use EXCEL => LSMW (Transform and map to IDOC) => generate IDOC => SAP EHS IDOC is booked

Many consultants are really experienced in using LSMW (and transformation pert) and the IDOC part is not that bad to use (never tried it; but we know it will work). For the "create" part this seems to be pretty straight forward; for the update part. you need to try (and do design etc.); but at the end you generate as well suitable IDOCs; and therefore it should work (in theory...) (and in your case you do not "update" but you do an "insert" (add data); and this is "simpler" than to do an update on existing data

This is the "best" approach to avoid many hours/days with design etc. At the end: decision depends on these questions:

a.) is this a "one and only" activity?

b.) should the end user be able to do it?

c.) etc.

So an number of questions (and their answers) have impact on the overall design

a.) the LSMW way to do it => not a useful tool for end user

b:) the standard import => not a useful tool for end user

c.) OCC => for key users this is an option

d.) ABAP for very experienced key usesr => yes this is an option (but as well: you do mass update !!! in most cases it is not easy to "revoke" the mass update)

C.B.

PS: i would be interested to know which option you will select and why....

[christoph_bergemann · Accepted solution]

Dear Sachin

only for completeness: by whatever reason: you can use "reference" in standard import.

For inheritance: we only option which I know is "IDOC" ..  Reference and inheritance have some clear differences (design etc.): in most cases referencing is not a bad option; inheritance as such has been optimized as well by SAP. PLease check the OCC part, I am not sure but may be inheritance is supported

C.B.

[Mark-Pfister · Accepted solution]

Hello all,

Christoph Bergemann wrote:

in principle: you can use EHS standard import (inheritance is not possible) and you can use OCC (not sure about inheritance, we are not using OCC for load purposes)


- assign inheritance relationships for each => not sure regarding OCC; to my knowlegde: not possiblel with "standard import"





PS: you need to understand the "inheritance" option; tehn you will understand that it is not easy to "populate" this by "import".

You can not load inheritance relationships with the standard import (*.dat files).

But you can load inheritance relationships with the help of the OCC Online mode. Please refer to the OCC documentation for details.

So with OCC you can load, delete update pretty much everything you can do in CG02 manually.

Kind Regards

Mark

[Ralph_P · Accepted solution]

Hi sachin,

there is no need for ABAP. Just create the dat-files for all properties you need to migrate. The actual load is then done in offline mode, so Citrix is no problem. The only thing you cannot do this way is the migration of inheritance relationships; they can only be loaded in online mode.

Ralph