cancel
Showing results for 
Search instead for 
Did you mean: 

Off-cycle PUOCBA issue

Former Member
0 Kudos

Hi,

We have issue with offcycle run, for all employees while doing "subsequent processes of off-cycle activities" cheques and payment summary is not generated. We have made sure we have maintained IT9 correctly, and wage type /559 is also generated for all employees. At the same time we have no issues in payroll run and posting, posting run is created successfully.

below is sample of error

Looking forward for your valuable inputs to resolve this.

Thanks

Babu

Accepted Solutions (1)

Accepted Solutions (1)

former_member235056
Active Contributor
0 Kudos

Hi Babu,

Firstly check if you ahve set-up house bank and its account ID in FBZP transaction under T012 and T012K tables.

Secondly, please check your DTAKT feature return values, it should be xxxxx/yyyyy/zzzz.

xxxxx is 5 character house bank code, if you have 4 characters only please place blank on 5th character place.

yyyyy is 5 character account id code, if you have 4 characters only please place blank on 5th character place.

zzzz is your paying company code if its same as sending company code for which you are entering this return value then you can ignore /zzzz.

This will remove T012 and T012K errors.

BNKA errors are probably because you bank key in IT0009 is not maintained with address data in bank master data table, please check BNKA table if bank address is entered with country also entered.

Thanks,

Ameet

Former Member
0 Kudos

Hi Ameet,

Thank you for details.

We have checked DTAKT and validated house bank code, account id and company code return values. BNKA and IT0009 data will not match for the reason it is cheque payment.

example IT0009

Any clues from here..

former_member235056
Active Contributor
0 Kudos

Hi,

Can you please provide details from table T012 and T012K for house bank and account id as well company code details from IT0001.

Also, provide DTAKT feature screenshot so I can assist.

Thanks,

Ameet

Former Member
0 Kudos

Hi Ameet,

Busy days!!

ok issue was resolved with SAP note: 2023449. It was an Authorization issue.

Thanks! Babu

Answers (0)