Call Transaction 'PA40' ALWAYS returns with error code

[Former Member]

Hi,

I'm having issues with updating personnel actions using CALL TRANSACTION 'PA40'. The call always ends with an error code.

I checked the message table and there are no error messages, only warnings and status messages. Warning and information messages are usually skipped in the BDC...I've coded an 'ENTER' to past the warning but this does not work either as the subsequent infotype screen fields are then not filled correctly.

The following values for addition OPTIONS are used:

data: opt like ctu_params.

opt-dismode = 'N'.

opt-updmode = 'A'. ('S' makes no difference)

opt-defsize = 'X'.

opt-nobinpt = 'X'. ( ' ' makes no difference)

I've tried using 'PA30' for the same actions but I get the same problem. I've used call transaction 'PA30' in many programs and I've never come across this problem.

Is there perhaps a config setting somewhere to fix this? I've tried hiring employees using HR_MAINTAIN_MASTERDATA with the employee existance check off but there's a couple of problems there as well - sample code for hiring an employee would be very helpful...

I need your help urgently and would appreciate your assitance immensely. (I'm working on 4.6C.)

Thank you.

LM

[Former Member]

Hi LM,

Have you tried your program in A mode and what was the outcome.

Regards,

Atish

[Former Member]

When executing in 'A' mode the record is updated successfully as I go past the warning message when pressing ENTER.

[Former Member]

That means you have not recorded for these warning messages in your BDC. You need to do the recorings for these also.

Regards,

Atish

[Former Member]

Ok, do I have to code the ENTER after each warning? I've tried this before and it didn't work but I will try it again. I've lost my connection to the system and will try again later.

Thanks.

[Former Member]

The easiest way to resolve this is to set

opt-dismode = 'E'.

this way it will run in background and jump out when it hits an error, and it's much easier to see what the real issue is.

I'm assuming you used SHDB first to get the recording?