Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP EHS Developments in version 4.7 and migration 6.0

eliseo_camacho_c
Discoverer
0 Likes
1,090

Hello Experts

Currently the company has implemented the SAP module EHS (Environment, Health, and Safety Management) in version 4.7 and Z programs were created to perform mass updates processes through BatchInput to EHSSERV01 and EHSTERM01 transactions.

They migrated from Version 4.7 to 6.0 and the Batch input stopped working since changed and now screens in Version 6.0 is used is the transaction EHSH_D_PCP- Planning Cockpit.

1 There is some BAPI or function module 6.0 to run in the background that has the same behavior EHSH_D_PCP or EHSSERV01 or EHSTERM01 tx.

2 Try again to create a new Batch Input of EHSSERV01 and EHSTERM01 transactions but does not take the Click Container.

Recording in SHDB:

When I run or process does not take the click Employee and does not advance.  It waits even though the recording was made

Example of the program running in the version 4.7 but 6.0 does not work.

Any suggestions.

Message was edited by: Eliseo Camacho Castillo

1 ACCEPTED SOLUTION
Read only

dairolozano
Contributor
0 Likes
970

Hi Eliseo.

Unfortuantely I don't have that module here in my instance, however please give a look to this discussion:

Please let me know if it works.

Regards,

Dairo

2 REPLIES 2
Read only

dairolozano
Contributor
0 Likes
971

Hi Eliseo.

Unfortuantely I don't have that module here in my instance, however please give a look to this discussion:

Please let me know if it works.

Regards,

Dairo

Read only

0 Likes
969


Solution:

SAP maintained backward compatibility, ie in version 6.0 programs exist Version 4.7, only SAP transactions associated eliminated to create a single transaction in 6.0 with new User Interface - Planning Cockpit.

ERP 4.7

ERP 6.0

TRANSACTION

PROGRAM

DESCRIPTION

TRANSACTION

PROGRAM

DESCRIPTION

EHSSERV01

EHS_SERVICE_OPEN

Create a Sequential Number for Medical Service

EHSSERV01

SAPLEHS00_PCP03

EHS: Planning Cockpit (Open Medical Service)

EHSTERM01

EHS_SCHEDULING

Schedule Dates for a Medical Service

EHSTERM01

SAPLEHS00_PCP03

EHS: Planning Cockpit (Scheduling medical service)

In 6.0, to keep in operation the developments flames through BDC Input Bath, create ZEHSSERV01 transactions and ZEHSTERM01 and some adjustment each Z programs that call the transaction previously mentioned by BDC- Bath Input.


Call transaction ZEHSSERV01

Call transaction ZEHSTERM01

For EHS_SERVICE_OPEN program: Create a Point Enhancement to validate the transaction code Z and assign default values:


Finally, SAP in Version .6.0 think the following module features the same functionality expected for each transaction:


TRANSACCION

MODULO DE FUNCION

EHSSERV01

EHS00_SERVICEOPEN00_ENTRY

EHSTERM01

EHS00_SCHEDULING00_ENTRY

What would we do without reference Debugger and use. Thanks Debugger ...!



I hope it useful for those implementations EHS-HCM module.