OCC Data upload and OCC connection

[satya11719]

Hi ,

Here i'm trying to upload some test data into specification workbench.

Steps i performed

1.I downloaded only EH&S OCC into my local desktop and i dont have Expert server linked to my SAP EHS system.

2. I was tried for online mode of transporting specification.

Made RFC with OCC , and i maintian data in rfc.ini also.

But still it is giving the above error.

Then i tried offlline with loading an Txt file in below format

Then i was try to upload to OCC for DAT file its giving error.

Either Table contain No data or there occured atleast one error while parsing file.

What are the exact prerequisites while doing offline mode in OCC.

In settings of OCC what exactly the path i have to give.

Please share your suggestions.

Thanks in Advance

Satya

[former_member408313 · Accepted solution]

Hi

Can you share the configuration you did in saprfc.ini. Against EHS_EXPERT what is the parameters you have mentioned and also what is the connection type (ABAP or TCP/IP) you have used to create the RFC in SM59 ?

Thanks and Regards

Jayakumar

[satya11719 · Accepted solution]

I was created RFC with same name like EHS_OCC now i maintained the same in SAPRFC.ini but i cant able to online import though OCC. I was created User exit EHS_OCC .

Thanks

Satya

[former_member408313 · Accepted solution]

Hi Satya,

1. You need to create program id with a simple EHS_OCC that would work, please remove the application path from the program id ($shell).

2. The connection should be ABAP connection that should not be TCP/IP, it should be type "A"

sample entries

DEST=EHS_OCC

PROGID=EHS_OCC

TYPE=A

GWHOSE and GWSERV as given above.

Thanks and Regards

Jayakumar

[Ralph_P]

Hi Satya,

the rfc-connection is needed to call the OCC from EHS for load of regulatory data. If you want to connect the OCC with EHS from the OCC side, you need to maintain the correct settings in the saprfc.ini and the destination of your call is surely not a system called EHS_OCC. So your entries in saprfc.ini are wrong, please check them,

For the offline mode, your file is missing a first row with comments. It doesn't matter what you write into the first row, but the OCC expects it anyway.

Ralph

[satya11719]

Hello Ralph,

Thank you , Welcome after long time.

If you any example of that RFC.ini connection could you please provide screenshot of rfc.ini n sm59 please.

so that i will set up the same.

Thanks

Satya

[former_member408313]

Hi Ralph / Satya

Not sure if you checked this info. The saprfc.ini file the entries for the R/3 system login information - Destination name for system is free text you can enter whatever you want to mention, it will not check for the exact name of your R/3 system. It can be D01 or even EHS_OCC. system will stop you from logging in. If it is a RFC enabled entries then destination entry matters like GENPC_IDT_800_1. So for this example, access saprfc.ini file based on your RFC_INI environmental parameter path and maintain below information

DEST=<your R/3 system for any suitable text>

TYPE=A

GWHOST = <HOST Info>

GWSERV = <sapgw00>

Thanks

Jayakumar

[Mark-Pfister]

Dear Satay,

I'm almost 100% positive that the R/3 System you are trying to connect to is not called "EHS_EXPERT".

Double check the documentation on how to connect the OCC to you SAP System fro data load.

Kind Regards

Mark

[satya11719]

Hi Mark,

Can you please send the document or link.

Thanks

Satya

[former_member408313]

Hi Satya,

Please check your saprfc.ini file settings under EHSOCC section. The file will be available in EHS Folder in the installation folder.

Thanks and Regards

Jayakumar

[former_member408313]

Hello Satya,

EHS OCC, EHS Rule Editor and EHS Expert are the three different things which comes with EHS Expert Installation file. EHS Expert requires Program id declaration in the saprfc.ini file (RFC.ini path if you are using EHS Management system). For EHS OCC / EHS Rule Editor you do not need do declare program id in saprfc.ini.

EHS OCC has two features I) To Load XML based Regulatory content and ii) Offline or online data load using dat / xls files. For these two features to work you need to i. create a RFC destination with "Start on Application server" and give $Shell\ehsocc.exe. and ii) Update saprfc.ini file with these variables

;EHS_OCC

DEST=EHS_OCC

TYPE=A

GWHOST = <HOST Info>

GWSERV = <sapgw00>

enter the EHS_OCC as R/3 system and maintain the log in information and check. So you need to modify your RFC destination in SM59 if it is not entered as above and then you need to use separate section to enter the OCC information in saprfc.ini file.

Thanks and Regards

Jayakumar

[satya11719]

Hello jaya Kumar ji,

After maintaining the RFC in particular OCC path ,And maintained userexit in system for OCC.

Still im not able to connect with SAP system with OCC.

Please help me on this.

Thanks

Satya

[former_member395773]

I am also getting the similar Issue . Not working at all . There is no clear guidance to do this connection from SAP .

[former_member408313]

Hi Prakash,

The RFC destination your are creating is required if you are using OCC for XML Loading. It is type "T" whereas for SAP OCC it is type "A".

To work with OCC for data load, you maintain the following information in saprfc.ini and try to log in

DEST=<System Name or Anyname like TEST>
TYPE=A (it should be A only"
ASHOST=From your system parameters put Host Name
SYSNR=Like 01

Log in with your user id

Thanks and Regards

Jayakumar

[satya11719]

Hi Jayakuamr ji,

Thanks for your mail,

1. You need to create program id with a simple EHS_OCC

EHS_OCC: is it standard program or other?

Can you please help me on this.

Thanks

Satya

[christoph_bergemann]

Dear Satya

check blog: https://blogs.sap.com/2014/11/13/rule-sets-secondary-data-determination/

You will find links to threads discussing "similar" issues

C.B.