Q
Problem solve Get help with specific problems with your technologies, process and projects.

Is it OK to use HTTP in 4.5 to move data to a non-SAP system?

I'm wondering if you have any concerns about using 4.5 with HTTP capability to move data to the non-SAP system. 4.5 lacks the WAS, which may inhibit HTTP use. If it's possible, how can I do this through SAP 4.5?

I have a CREMAS IDoc message created from 4.5B and I want to post it into non-SAP system through HTTP.

I'm wondering if you have any concerns about using 4.5 with HTTP capability to move data to the non-SAP system....

4.5 lacks the WAS, which may inhibit HTTP use. If it's possible, how can I do this through SAP 4.5?

Indeed, Kernel 4.5 has no built-in HTTP support, but you can nevertheless send out data via HTTP. The way to do it is to use the function HTTP_POST via the RFC destination SAPHTTP. The latter should be defined in your system. If you do, it should point to a utility program "saphttp", found in the SAP binaries directory.

Some examples how to use it can be found at my site, http://logosworld.com, in the mySAP/Netweaver section.

Here is an example of a query with HTTP_POST. (Please mind to insert a meaningful URL that you can access from the SAP application server).

DATA: ABSOLUTE_URI(128) type c.
data: response_headers(80) occurs 0 with header line.
data: RESPONSE_ENTITY_BODY(120) occurs 0 with header line.
ABSOLUTE_URI =
'http://xml.amazon.com/onca/xml2?t=webservices-20' &
'&tag=logosworldcom&dev-t=D2H3YO46KJJ615' &
'&AsinSearch=3528057297&type=lite&f=xml'.
CALL FUNCTION 'HTTP_GET'
  EXPORTING
    ABSOLUTE_URI                      = ABSOLUTE_URI
    RFC_DESTINATION                   = 'SAPHTTPA'
    PROXY                             = '192.168.69.64:8080'
* IMPORTING
*   STATUS_CODE                       =
*   STATUS_TEXT                       =
*   RESPONSE_ENTITY_BODY_LENGTH       =
  TABLES
*   REQUEST_ENTITY_BODY               =
    RESPONSE_ENTITY_BODY              = RESPONSE_ENTITY_BODY
    RESPONSE_HEADERS                  = RESPONSE_HEADERS
*   REQUEST_HEADERS                   =
  EXCEPTIONS
    CONNECT_FAILED                    = 1
    TIMEOUT                           = 2
    INTERNAL_ERROR                    = 3
    TCPIP_ERROR                       = 4
    DATA_ERROR                        = 5
    SYSTEM_FAILURE                    = 6
    COMMUNICATION_FAILURE             = 7
    OTHERS                            = 8
          .
IF SY-SUBRC >< 0.
  write: / sy-subrc.
ENDIF.
loop at response_entity_body.
  write: / response_entity_body.
endloop.
This was last published in June 2005

Dig Deeper on SAP Web applications

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close