Question:
Hi,
Post upgrade to EBP 3.0, the development system OCI call to a vendor catalog is not working (despite being fully functional in the pre Upgrade EBP 2.0 Production system in the same format).
The call structure is:
1 https://www.XXXXX.asp URL
10 LOGINID password Fixed value
20 LOGINPWD 53036B Fixed value
30 HOOK_URL Return URL
40 ~CALLER CTLG Fixed value
50 ~TARGET _top Fixed value
60 ~OkCode ADDI Fixed value
and the error message that we receive on punchout is:
Invalid PunchOut request, cannot continue...
~OKCode field is missing
~Target field is missing
~Caller field is missing
If we change the OCI call structure to have the HOOK_URL as the final perameter, the catalog will allow punch out but will not check back to EBP.
I have also incorporated a ~ForceTarget perameter to no avail.
The ITS (version 6.10) port for Secure socket layer is specified and all internally hosted catalogs are functioning fine.
Any assistence or pointers in this matter would be gratefully appreciated.
Regards,
CB
Answer:
Hi CB,
We are experiencing exactly the same problem with the punchout as yourself. Please can you let me know if you have resolved this issue and if so, what did you do.
Regards
Monty
Answer:
Hi CB,
We have actually resolved our problem, however I am not sure if we should have to do it in the way that we have.
In the BADI BBP_CAT_CALL_ENR I added the following code :-
* Ensure that okcode, target and caller fields are added to the
* BIOMNI catalog call only.
read table ct_post_values into ws_post_values
with key fieldname = 'LOGINID'.
if ws_post_values-fieldcont = 'xxxxxx'. (where xxxxx is the cat. login id)
clear ws_post_values.
ws_post_values-fieldname = '~OKCODE'.
ws_post_values-fieldcont = 'ADDI'.
append ws_post_values to ct_post_values.
clear ws_post_values.
ws_post_values-fieldname = '~TARGET'.
ws_post_values-fieldcont = '_top'.
append ws_post_values to ct_post_values.
clear ws_post_values.
ws_post_values-fieldname = '~CALLER'.
ws_post_values-fieldcont = 'CTLG'.
append ws_post_values to ct_post_values.
endif.
This effectively adds the ~OkCode, Target and caller fields with their respective values to the end of the agate table. The catalog then recognises these fields and we are able to punchout.
I do hope that this will help you as well. Let me know how you get on.
Regards
Monty
Answer:
Hi,
It it possible to emulate a punch-out, for example
We have a senario here where we want to integrate with a supplier
The punch-out logs you into the suppliers web site, but we don't have SAP enterpise buyer.. so we want to emulate the punch-out
One the users finishes using the supplier's shopping basket we want XML to be sent to our internal procurement system....
How might this be achived?
The oci punch-out just looks like a HTML post to me...
Regards