SAP API_S2K_IP_HDR_CREATE Function Module for Update Header table for SPEC2000 Upload









API_S2K_IP_HDR_CREATE is a standard api s2k ip hdr create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Header table for SPEC2000 Upload processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for api s2k ip hdr create FM, simply by entering the name API_S2K_IP_HDR_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ADS2KIPUPL_API_AL
Program Name: SAPLADS2KIPUPL_API_AL
Main Program: SAPLADS2KIPUPL_API_AL
Appliation area:
Release date: 23-Sep-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function API_S2K_IP_HDR_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'API_S2K_IP_HDR_CREATE'"Update Header table for SPEC2000 Upload
EXPORTING
IS_UPDATE_OPTIONS = "Update Options
IS_SPCIPHDR = "Stores header information for IP data
IS_SPCIPHDRT = "Text for SPCIPHDR - for every SQNBR

IMPORTING
ES_UPLOAD_STATUS_HDR = "Upload status
ES_SPCIPHDR = "Stores header information for IP data
ES_SPCIPHDRT = "Texts for SPCIPHDR - for every SQNBR

TABLES
T_MESSAGES = "SPEC2000 IP Upload: Message Communication Structure
T_MESSAGES_DOC_PARAMS = "SPEC2000 IP Upload: Msg Comm Struct-SAPScript Doc Parameters
* T_SPCIPEXTN = "SPEC2000 Initial Provisioning: Extensions
.



IMPORTING Parameters details for API_S2K_IP_HDR_CREATE

IS_UPDATE_OPTIONS - Update Options

Data type: API_SPCIP_HDR_OPTIONS
Optional: No
Call by Reference: No ( called with pass by value option)

IS_SPCIPHDR - Stores header information for IP data

Data type: API_SPCIPHDR
Optional: No
Call by Reference: No ( called with pass by value option)

IS_SPCIPHDRT - Text for SPCIPHDR - for every SQNBR

Data type: API_SPCIPHDRT
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for API_S2K_IP_HDR_CREATE

ES_UPLOAD_STATUS_HDR - Upload status

Data type: API_SPCIP_UPLOAD_STATUS_HDR
Optional: No
Call by Reference: No ( called with pass by value option)

ES_SPCIPHDR - Stores header information for IP data

Data type: SPCIPHDR
Optional: No
Call by Reference: No ( called with pass by value option)

ES_SPCIPHDRT - Texts for SPCIPHDR - for every SQNBR

Data type: SPCIPHDRT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for API_S2K_IP_HDR_CREATE

T_MESSAGES - SPEC2000 IP Upload: Message Communication Structure

Data type: ADS2KIPUPL_MSG_COMM
Optional: No
Call by Reference: Yes

T_MESSAGES_DOC_PARAMS - SPEC2000 IP Upload: Msg Comm Struct-SAPScript Doc Parameters

Data type: ADS2KIPUPL_MSG_COMM_DOC_PARAMS
Optional: No
Call by Reference: Yes

T_SPCIPEXTN - SPEC2000 Initial Provisioning: Extensions

Data type: API_SPCIPEXTN
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for API_S2K_IP_HDR_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lt_t_messages  TYPE STANDARD TABLE OF ADS2KIPUPL_MSG_COMM, "   
lv_is_update_options  TYPE API_SPCIP_HDR_OPTIONS, "   
lv_es_upload_status_hdr  TYPE API_SPCIP_UPLOAD_STATUS_HDR, "   
lv_es_spciphdr  TYPE SPCIPHDR, "   
lv_is_spciphdr  TYPE API_SPCIPHDR, "   
lt_t_messages_doc_params  TYPE STANDARD TABLE OF ADS2KIPUPL_MSG_COMM_DOC_PARAMS, "   
lt_t_spcipextn  TYPE STANDARD TABLE OF API_SPCIPEXTN, "   
lv_es_spciphdrt  TYPE SPCIPHDRT, "   
lv_is_spciphdrt  TYPE API_SPCIPHDRT. "   

  CALL FUNCTION 'API_S2K_IP_HDR_CREATE'  "Update Header table for SPEC2000 Upload
    EXPORTING
         IS_UPDATE_OPTIONS = lv_is_update_options
         IS_SPCIPHDR = lv_is_spciphdr
         IS_SPCIPHDRT = lv_is_spciphdrt
    IMPORTING
         ES_UPLOAD_STATUS_HDR = lv_es_upload_status_hdr
         ES_SPCIPHDR = lv_es_spciphdr
         ES_SPCIPHDRT = lv_es_spciphdrt
    TABLES
         T_MESSAGES = lt_t_messages
         T_MESSAGES_DOC_PARAMS = lt_t_messages_doc_params
         T_SPCIPEXTN = lt_t_spcipextn
. " API_S2K_IP_HDR_CREATE




ABAP code using 7.40 inline data declarations to call FM API_S2K_IP_HDR_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!