cancel
Showing results for 
Search instead for 
Did you mean: 

CG36 usable for business

gernotditten
Explorer
0 Kudos

Dear experts,

we set up our system to also upload inbound documents like supplier SDS, REACH information sheets on Raw Materials etc.

There are still a lot of documents that weren't uploaded yet. The business can do it one by one in CG36VEN. The upload of a whole bunch from a daughter company is done by an external consultant via CG36.

Now I was asked if it is not possible to hand over CG36 to the business. According to my knowledge the creation of the input file is not easy. I'm not an expert here.

Did anybody of you had a similar requirement and how was this solved? Or maybe you can come up with ideas?

My ideas are:

1) Writing an ABAP where you can upload some file and that creates the file structure for CG36 (and provides all checks) and then call CG36 directly (for sure access to the import folder must be given so that the documents can be put there).

2) Call CG36VEN multiple times in a program filling the relevant fields also from an imported file in an LSMW.

Thank you in advance.

Best regards,

Gernot

Accepted Solutions (0)

Answers (2)

Answers (2)

Ralph_P
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Gernot,

I understand you need a possibility to create the dat-files necessary for the mass import of inbounds. Why don't you create an Excel macro that reads in the names of the pdf-files. Other needed information like language, version, country etc. can be entered quite easily into the Excel file using existing functionalities or simply manually. Via another Excel macro you can then create all dat-files.

Ralph

christoph_bergemann
Active Contributor
0 Kudos

Dear Ralph

SAP uses the term "key" file and not "dat" file if you import e.g. pdf files

regarding:

"Other needed information like language, version, country etc. can be entered quite easily into the Excel file using existing functionalities or simply manually"

It depends on your definition of "easy". I call it "time consuming". From user point of view: may be easy.

Using an EXCEL macro you can do a "lot" (for usibility etc.).

If you import the names of the pdf file using such a "macro" you must any how be able to consume data like specify spec id , generation variant (or country) and language (and the last three informations must be specified (in most cases) by the user) per "pdf" file to generate the "key" file and you still need the "SAP application folder" step to use CG36; and to upload the key and pdf files can be a "time consuming" step (depending on the security framework of your company..) (if you are using SAP standard options).

C.B.

christoph_bergemann
Active Contributor
0 Kudos

Dear Gernot

regarding:

2) Call CG36VEN multiple times in a program filling the relevant fields also from an imported file in an LSMW.

I am not aware of any option to use here LSMW direct.

Regarding:

1) Writing an ABAP where you can upload some file and that creates the file structure for CG36 (and provides all checks) and then call CG36 directly (for sure access to the import folder must be given so that the documents can be put there).

To use "CG36" you need

1.) very high access rights

2.) you need access to some "SAP application folders" (in most cases on UNIX level)

Therefore: in > 80 % of the cases the "move" of the documents is done by conultants (in most cases external) as the need to do an import is only rare

Coming back to ABAP

Any kind of report (Inbound (Pdf)) or normal WWI can be distributed by using "ALE"

Here now in theory LSMW comes in place. LSMW can generate "ALE" data structures

Never seen one company using this alternative.

Using CG36VEN you can not do an upload to the so called "document class" (Doc-X export/import). This is oly possible using CG36.

The issue is not the ABAP part. The problem is the "input" (refering to "Now I was asked if it is not possible to hand over CG36 to the business. According to my knowledge the creation of the input file is not easy. I'm not an expert here.)

and yes you are correct. The input file is "easy" ( i can not confrim that it is not easy to understand the structure) but it is very time consuming to generate it as you need to do it "one by by one" and there is no real option for "automating" something

You would need an EXCEL file like:

doument file name; spec ID, Generation variant, Language

Defining the "target" (this is the "key" file). Then you can consume this using ABAP (+ the document).

If you design the ABAP correct: You can upload the documents from your "client" and avoid the use of SAP application folders.

Overall: sorry to say: this is a customer specific topic. Any company use a different solution.

C.B.

PS: check e .g. https://blogs.sap.com/2017/09/04/data-migration-in-ehs-classic/

But you will find many similar questions/discussions here

e.g. like https://answers.sap.com/questions/12966823/sap-ehs-data-migration-of-from-ecc-to-s4.html

https://answers.sap.com/questions/12852451/cg36ven-additional-information.html

https://answers.sap.com/questions/12981710/report-import-using-cg36cg36ven.html

https://answers.sap.com/questions/12270764/import-reports---create-key-file.html