Inbound Proxy don't create objects

[Former Member]

Hello guys,

I have a problem with my proxy. When we debug the proxy with transaction sproxy, the objects are created, but when we send the information by PI the objects are not created. We have also a call to an outbound proxy if there is an error to send a mail, debugging the proxy the mail is sent, but when we execute by PI nothing is done.

My code start with:

APPEND input TO proxy.

LOOP AT proxy INTO proxy_wa.

Here we create the objects type BUPA and at the end we do the next calls:

CALL FUNCTION 'BUPA_CENTRAL_EXPL_SAVE'.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

WAIT = 'X'

IMPORTING

return = return_commit.

ENDLOOP.

After the Loop we have a variable with the errors to call an outbound proxy and we do:

DATA: proxy_error TYPE REF TO zdpi_co_si_out_host_error_prox,

fault TYPE REF TO cx_ai_system_fault.

• Llamamos al proxy para enviar el mail

CREATE OBJECT proxy_error.

TRY.

APPEND log_data_proxy-log_line TO tabla_error-error.

error-mt_host_error_proxy = tabla_error.

CALL METHOD proxy_error->si_out_host_error_proxy

EXPORTING

output = error.

COMMIT WORK

.

CATCH cx_ai_system_fault INTO fault .

CREATE OBJECT fault.

WRITE 😕 fault->errortext.

ENDTRY.

Do you know why the objects are not created when we send the information by PI?

Maybe we have to do a commit work in the code?

Many thanks in advance.

Regards,

Xavi.

Edited by: Xavi Carb on Mar 5, 2010 9:42 AM

[MichalKrawczyk · Accepted solution]

Hi,

>>>Maybe we have to do a commit work in the code?

1. you don't commit in asyn proxies - they are commited by the proxy framework

2. maybe the user that is used for PI communication has less authorization then the one you use

in TEST mode ?

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Hello Michal,

We use a user of type C (communication). The role is SAP_SLD_CONFIGURATOR and the Profiles are SAP_ALL and S_A.SCON.

The user I used in CRM is of type D (Dialog) with profiles SAP_ALL and T_AG210005 and T_AG210011. It has different roles like SAP_BC_USR_CUA_CLIENT, SAP_CRM_OR_USER, SAP_CRM_UIU_FRAMEWORK, SAP_CRM_UIU_MKT_PROFESSIONAL, SAP_CRM_UIU_SLS_PROFESSIONAL.

Also the parameters are different. The C type has parameter WLC ( workflow ) and my user has BSPWD_USER_LEVEL ( User level ), POK, SCL and WLC.

Maybe this could be the problem?

Many thanks.

Regards,

Xavi.

[Former Member · Accepted solution]

Hi Xavi,

Why can't u use the below user to test and confirm the reason for failing is authorization or not ?

-

---

The user I used in CRM is of type D (Dialog) with profiles SAP_ALL and T_AG210005 and T_AG210011. It has different roles like SAP_BC_USR_CUA_CLIENT, SAP_CRM_OR_USER, SAP_CRM_UIU_FRAMEWORK, SAP_CRM_UIU_MKT_PROFESSIONAL, SAP_CRM_UIU_SLS_PROFESSIONAL.

-

---

ABAP proxy receiver- SAP_XI_APPL_SERV_USER (additional application-specific authorizations required). both service users XIAFUSER and XIISUSER must be assigned the SAP_XI_APPL_SERV_USER role.

Thanks,

RJ

[stefan_grube]

> CATCH cx_ai_system_fault INTO fault .

> CREATE OBJECT fault.

> WRITE 😕 fault->errortext.

> ENDTRY.

Write statement is useless.

Throw an exception to see the errors.

[Former Member]

Hi Xavi,

I got same issue.This is related to Authorization issue.In RFC destination u have used one userid.This user id doesn't have necessary authorization.In rfc destination u have to use service user or Dialog user.Please ask u r Basis Team to provide necessary authorizations.

Thanks

Ravi