BAPI TRANSACTION COMMIT not working in production SAP system

[Former Member]

I am currently calling the BAPI BAPI_BUPA_ADDRESS_ADD and the BAPI BAPI_TRANSACTION_COMMIT after BAPI BAPI_BUPA_ADDRESS_ADD. The process is working in my development system and QA system but not in production system. The input values to BAPI_BUPA_ADDRESS_ADD are populated when I do the call. For some reason the Addresses are not created or updated in Production but are updated and created in the other systems. Any ideas on what could be causing this?

STEP1:

CALL FUNCTION 'BAPI_BUPA_ADDRESS_ADD'

IN BACKGROUND TASK

AS SEPARATE UNIT

EXPORTING

businesspartner = wa_cs009_infile-buspartner

addressdata = aperdatab

accept_error = zif_ut=>cc_on " no errormessages for regional structure

IMPORTING

addressguid = lv_address_guid

TABLES

bapiadtel = aperteltab

bapiadfax = aperfaxtab

bapiadsmtp = apersmtptab

bapiad_rem = aperadremtab.

STEP2:

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

wait = ''.

[Former Member]

I am currently calling the BAPI BAPI_BUPA_ADDRESS_ADD and the BAPI BAPI_TRANSACTION_COMMIT after BAPI BAPI_BUPA_ADDRESS_ADD. The process is working in my development system and QA system but not in production system. The input values to BAPI_BUPA_ADDRESS_ADD are populated when I do the call. For some reason the Addresses are not created or updated in Production but are updated and created in the other systems. Any ideas on what could be causing this?

STEP1:

CALL FUNCTION 'BAPI_BUPA_ADDRESS_ADD'

IN BACKGROUND TASK

AS SEPARATE UNIT

EXPORTING

businesspartner = wa_cs009_infile-buspartner

addressdata = aperdatab

accept_error = zif_ut=>cc_on " no errormessages for regional structure

IMPORTING

addressguid = lv_address_guid

TABLES

bapiadtel = aperteltab

bapiadfax = aperfaxtab

bapiadsmtp = apersmtptab

bapiad_rem = aperadremtab.

STEP2:

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

wait = ''.

[former_member156446]

what are you seeing in RETURN table after the main bapi call...

Do you see lv_address_guid getting populated?

[peter_ruiz2]

Hi Steve,

Have you tried entering data manually in PA30 for IT0006? Check first if you have the right authorization to maintain Addresses in PA30.

Regards,

Peter

[Former Member]

Hi Steve,

Try passing WAIT = 'X' to the BAPI_TRANSACTION_COMMIT FM.

Regards,

Ganga

[Former Member]

Hi Steve,

Could it be an authorization issue?

Brenda

[Former Member]

The problem was with authority on the BATCH userid that was used to run the job in the production system. The batch userid did have the correct authority to perform updates in the development and QA systems thats why it was working in those systems. I appreciate the responses from this forum in pointing me in the right direction.

Thanks,

Steve Atlas

Edited by: Steve Atlas on Aug 4, 2011 10:25 PM