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.