SAP OSS Notes

2020325 SAP OSS Note - ELStAM: Improvements and corrections 19/2014








SAP OSS Note 2020325 version 0001 contains details of a know issue related to ELStAM: Improvements and corrections 19/2014 . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 2020325 Details:





When does this problem occur



This SAP Note delivers corrections for errors detected during operation


and improvements to the ELStAM procedure (electronic employmen

t tax deduction features).




Cause of the problem and Pre-requisites



The following points have been adjusted:


,,Report RPCE2AD0_IN ("ELStAM Procedure: Request to Clearing House for
Confirmations")

,,(1) When you retrieve the change lists from the clearing house, the


system will, in future, check whether the employer tax numbers (A

GSTNR) they contain also exist in the SAP system. If this is not the


case, the system will issue a warning. The new check is intended

to create a link between the new AGSTNR and an AGSTNR that already


exists in the system. If a link is created, both AGSTNRs are displa

yed in the warning. Background: Due to a change to the AGSTNR by the tax


office, change lists may be provided that use the new AGSTNR

even though the notifications occur under the old AGSTNR and the new


AGSTNR is not yet entered in the table T5D0P.

,,Report RPCE2SD0_IN ("ELStAM Procedure: Transfer XML Data into ELStAM


Table")

,,(1) If the outbound process for notifications was deleted in the B2A


Manager, a program termination occurs during the transfer of ELS

tAM data from the change list. The runtime error GETWA_NOT_ASSIGNED


occurs.

,,This has been corrected. In this case, the system will issue a warning


message. In this case, it is not possible to update the outbou

nd process.




Solution instructions



Implement the correction instructions or import the HR Support Package


specified.









Description of problem



RPUE2AD0, RPCE2SD0_IN







------------------------------------------------------------------------

|Manual Pre-Implement. |

------------------------------------------------------------------------

|VALID FOR |

|Software Component SAP_HRCDE SAP HR Germany |

| Release 600 SAPK-600A2INSAPHRCDE - SAPK-600A9INSAPHRCDE |

| Release 604 SAPK-60468INSAPHRCDE - SAPK-60475INSAPHRCDE |

| Release 608 Until SAPK-60803INSAPHRCDE |

------------------------------------------------------------------------



Create messages:

===================

Call transaction SE91. Enter the message class HRPAYDEE2.

(1) Enter the message number 275. Choose "Change".

Message short text: "Status update for outbound process in B2A Manager
(GLBID <(>&<)>1) not possible"



Copy the following long text:



<(>&<)>CAUSE<(>&<)>

When checking the GLBID <(>&<)>1 for the status update of the outbound
process it was determined that no entry



with this key (table PB2AMGR, field GLBID) was found.

It is likely that the entry was deleted.



<(>&<)>SYSTEM_RESPONSE<(>&<)>

The status of the outbound process can no longer be updated in B2A.



<(>&<)>What_TO_DO<(>&<)>

Prevent such constellations in the future by first deleting completely
processed processes from the



B2A Manager as part of a reorganization.



Save the new message.





(2) Enter the message number 355. Choose "Change".

Message short text: AGSTNR <(>&<)>1 not available in system; existing
assignment AGSTNR <(>&<)>2



Copy the following long text:



<(>&<)>CAUSE<(>&<)>

The provided change list contains the employer tax number (AGSTNR). This
does not



exist in the system. However, the system was able to use the processing
data ticket (NDTIC) provided



with the change list to establish a link to AGSTNR.



<(>&<)>What_TO_DO<(>&<)>

Check whether the AGSTNR was replaced with AGSTNR due to a change of tax
number. If this is the



case, perform the necessary Customizing steps to maintain the new tax
number in the system.



Save the new message.





(3) Call transaction SE91. Enter the message class HRPAYDEE2.

Enter the message number 356. Choose "Change".

Message short text: Assignment of NDTIC <(>&<)>1 and AGSTNR <(>&<)>2 not
possible



Copy the following long text:



<(>&<)>CAUSE<(>&<)>

An employer tax number (AGSTNR) that does not exist in the system was
found in a change list



(response to registration/change of registration/deregistration).



<(>&<)>SYSTEM_RESPONSE<(>&<)>

The processing data ticket (NDTIC) also available in the change list
was then used to attempt to establish



a connection to an AGSTNR that exists in the system. During this attempt
it was determined that



table V_P01E2_STATUS does not contain an entry for NDTIC.



<(>&<)>What_TO_DO<(>&<)>

Clarify why change lists with the AGSTNR were provided for your data
provider.



Save the new message.







(4) Enter the message number 357. Choose "Change".

Message short text: AGSTNR <(>&<)>1 in change list (<(>&<)>2) not
available in the system



Copy the following long text:



<(>&<)>CAUSE<(>&<)>

The clearing house provided a change list () with an employer tax number
(AGSTNR)



that does not exist in the system.



<(>&<)>SYSTEM_RESPONSE<(>&<)>

The AGSTNR could not be found in the system.



<(>&<)>What_TO_DO<(>&<)>

Clarify why change lists with the AGSTNR were provided for your data
provider.



Save the new message.

Solution instructions


Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 2020325 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 2020325 has already been downloaded and is valid


To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 2020325 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.



If note 2020325 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)