Solution : https://service.sap.com/sap/support/notes/647145 (SAP Service marketplace login required)
Summary :
HR-PDC communication issues reported stem from absence of proper Customizing for subsystem connectivity. To resolve, undertake the following steps: 1) Set up an RFC destination in SM59, ensuring subsystem registration and start via SAP system. 2) Establish a port using WE21, linking to the RFC destination for IDoc transfers. 3) Define a logical system for the subsystem in BD54 and verify the client’s system in SM30. 4) Configure partner profiles in WE20, adding required parameters for message types. 5) Build a distribution model in BD64 for both outbound and inbound data links, including necessary BAPIs. Finalize by testing transactions PT80, WE05, and SM58 to ensure correct Customizing and operational connectivity.
Key words :
outbound parameter table message types - basic typeshrcc1dnattab hrcc1dnattab01hrcc1dnbalan hrcc1dnbalan01hrcc1dncostc hrcc1dncostc01hrcc1dnextwt hrcc1dnperso01hrcc1dninord hrcc1dninord01hrcc1dnobjid hrcc1dnobjid01hrcc1dnperso hrcc1dnperso01hrcc1dntevgr hrcc1dntevgr01hrcc1dnwbsel hrcc1dnwbsel01hrcc1requpextwt hrcc1requpextwt01hrcc1requpteven hrcc1requpteven01 choose, enter 20'transfer idoc immed' add inbound parameters, hrcc1upteven enter process code 'bapi', select 'idoc record types 4, input parameter table, add outbound parameters, 'create outbound parameter', choose 'create model view', status 53 'application document posted', message types
Related Notes :
| 176927 | Transceiver component becomes unnecessary |