Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8623

Re: Invalid parameter SECONDARY_RECORD-PSKEY Error in Dependent/Family Member Screen

$
0
0

There could be several possible causes

 

Usually this error occurs if a secondary infotype functionality has been delivered via SP or SNOTE for infotype 0002 but the PERNR you are using does not have secondary infotype record

 

Tables V_T582V & V_T582W determine if a secondary infotype will be used - if you remove entries here this will deactivate the secondary infotype useage - this might be one way to resolve the issue - but perhaps you wish to use the secondary infotype - in some cases it might be required- for example ESS might expects a secondary infotype and throw an error if there is an issue

 

If you wish to use the secondary infotype you need the delivered entries in V_T582V & V_T582W and you need to run RPUPAV00 for any PERNR that has a 0002 record existing prior to the new secondary infotype being introduced to ensure they have a secondary infotype record key that matches the primary infotype key

 

Regards


Viewing all articles
Browse latest Browse all 8623

Trending Articles