BAPI_BUS1077_create_specification

[Former Member]

Hello Everybody,

For our customer we need to load en large numbers of specifications complete with properties. I found BAPI_BUS1077_CREATE_SPECIFICATION, but thats not clear to us. Is there some one who is able to give us detailed instructions how to load the specs with this function. Also templatse for the loadfiles are needed.

Thanks in advance.

Kees

[christoph_bergemann · Accepted solution]

Dear Kees

why not using standard import functionality of EHS? This is the standard approach used.

Approach has been discussed often here. Check e.g. http://scn.sap.com/docs/DOC-41109

Check e.g.:

http://help.sap.com/erp2005_ehp_06/helpdata/en/a7/28792d0a6c11d28a220000e829fbbd/content.htm?framese...

with reference to the two important chapters:

Specification Import

Importing Specifications

Some companies used in the past "DataEditor" of TechniData which might be available now as a service from SAP.

The BAPI you have mentioned is used rarely to do the job

In any case: may be check:

http://scn.sap.com/thread/741589

http://help.sap.com/erp2005_ehp_03/helpdata/en/fb/aa3bfbf89b11d287d8080009b98822/content.htm

http://www.se80.co.uk/sapreports/r/rc1_/rc1_1077_bapi_example_change.htm

There are additional example reports available but If I remember correct not in context of:

BAPI_BUS1077_create_specification

Hope this helps.

C.B.

PS: http://scn.sap.com/thread/2154501 could be of interest as well

[Former Member · Accepted solution]

Hello Christoph,

We will try to see if it's working oke. Keep you informed.

Kees

[christoph_bergemann · Accepted solution]

Dear Kees

the "input format" used by SAP EHS standard import is not easy to understand. Many people try therefore to get familiar with this tool the other way around by first "exporting" something and analysing the result to get a good understanding about how to handle the import.

It is recommended to at least do the import with one identifier (e.g. NAM PROD; and my be a spec header note information). Then you can go on step by step (e.g. add data in VAT: "form", "state of matter" etc. and then increas complexity (e.g. VATs like "Standard Composition".

PAY ATTENTION: the import is not as strict as CG02. Therefore take your time to "play" with the interface in "Dev" system.

Check online help especially chapter: " Specification Import Control" and take your time to understand the import parameters.

Keep in mind: depending on your set up there are some nice "pitfalls" in using this interface. To my knowlede the OCC (Open Content Connector) can be used only if the spec id is existing; in your case it will not help therefore; but may be it is a good idea to check alternatives for uploading data.

C.B.

[christoph_bergemann · Accepted solution]

Dear Kees

congratulation. You started your own blog . http://scn.sap.com/people/kees.leautaud/blog

Don't be to pessimistic regarding the standard import/export functionality of EHS (and  I assume you will have may be chances to come into contact with "Component Extension" solution as import etc. is different there).

Keep in mind (check some parallel threads): you can not upload "inheritance data" with standard import. New features of EHS are as well not supported by EHS (refer to SAP online help; they are explaining the limitations to a certain extent).

And yes according to your blog: you are right;: the import file structure of EHS is not "nice" and there are as well some other pitfalls in the process (depending on Operating system of SAP (Unix or different one); keep in mind: the import is not as strict as CG02; therefore you can upload data which you cannot maintain using CG02 (in in most cases you need to use "debug and replaxce to get rid of the "issues").

It is not only crucial to understand the import file structure; the upload selection screen with the many selection options is "hard" to understand if you do the job for the first time. Give it a try (on e.g. dev system) and learn from experience (hopw to use the screen; to understand the options etc.).

PS: don't get "panic" if the export files (or import file) might have a "large size" (> 100 MB). And keep in mind: To detect import errors (and their reason) is not simple as the "logging feature" of EHS does not always help you to find the problem.

The import of "reports" is a little bit "simpler". The same is true for phrase upload.

C.B.