Problem with external punchout in SRM Server 713

[Former Member]

Hello,

We upgrade from SRM_SERVER 701 SP 04 to SRM_SERVER 713 SP 02, now we have a problem with external catalog, we did not change anything in standard call structure, however now when the user access to external catalog, select a product and "checkout", SRM returns to shopping cart screen without products and no message are register in log in transaction code SLG1.

Our parameters in structure are:

10                     https://xxxxxxxxx                          URL

20 VIEW_ID          NAME                            Fixed value

30 VIEW_PASSWD     XXXXXX               Fixed value

40 USER_ID          SY-UNAME                   SAP field

50 BRANDING      search5                     Fixed value

60 LANGUAGE      ES                           Fixed value

70 COUNTRY      MX                             Fixed value

75 EASYORDER 1                          Fixed value

80 target _top                                  Fixed value

85 ~caller      CTLG                              Fixed value

90 OCI_VERSION     4.0                     Fixed value

91 FILTER                                      Fixed value

92 OPI_VERSION 1.0                     Fixed value

100 HOOK_URL                             return URL

110 returntarget      _top                       Fixed value

we made some test with parameter BYPASS_INB_HANDLER, set as 'X' but this not solve our issue.

We have an implementation in badi BBP_CATALOG_TRANSFER to map product category, even if I set an external breakpoint in this implementation, system does not pass through it, also we test with this implementation inactive and behavior is the same, nothing transfer to shopping cart

Does anyone know what's missing?

Thanks in advance.

Best regards,

José Luis D.

[Former Member · Accepted solution]

Hello,

mi problem solved with SAP note 2010345, we upgraded NWBC and all works fine now.

José Luis

[jason_boggans]

Dear Jose Luis,

Please debug the catlaog transfer and check the et_messages table to see what errors are being raised, see the KBA here for details on debugging this if you're not familiar with it.

Regards,

Jason

[Former Member]

Hello Jason,

Thank you for your answer, but as I told, If I set an external breakpoint it does not stop for debugging, so I can't see table as you recomended. This process (debugging) is familiar to me, in last version I can do it.

Any suggestion?

Thanks in advance, best regards

José Luis D