SAP OIJ_EL_GTM_TSW_DOCG_REVERSE_TC Function Module for CIP FM to reverse Trading Contract









OIJ_EL_GTM_TSW_DOCG_REVERSE_TC is a standard oij el gtm tsw docg reverse tc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CIP FM to reverse Trading Contract 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 oij el gtm tsw docg reverse tc FM, simply by entering the name OIJ_EL_GTM_TSW_DOCG_REVERSE_TC into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIJ_EL_GTM_TSW_DOCG
Program Name: SAPLOIJ_EL_GTM_TSW_DOCG
Main Program: SAPLOIJ_EL_GTM_TSW_DOCG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function OIJ_EL_GTM_TSW_DOCG_REVERSE_TC 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 'OIJ_EL_GTM_TSW_DOCG_REVERSE_TC'"CIP FM to reverse Trading Contract
  EXPORTING
   I_TICKET_HEADER =  "Universal ticket table
   I_TICKET_ITEM =  "Universal ticket item table
   I_OIJNOMH =  "Nomination Header
   I_OIJNOMI =  "Nomination Item
   I_OIJIMPORT =  "TSW: Parameter imported to CIP functions
   I_TKT_I_O1 =  "Appendix: TSW Ticket item - Conversion Parameters

CHANGING
*  CT_TICKET_HEADER_EVT =  "Ticket Events Table Type
*  CT_TICKET_HEADER_EVT_TXT =  "TSW: table type to roij_txt
*  CT_TICKET_ITEM_EVT =  "Ticket Events Table Type
*  CT_TICKET_ITEM_EVT_TXT =  "TSW: table type to roij_txt
*  CT_TICKET_HEADER_EVT_PV =  "Ticket Events Table Type
*  CT_TICKET_HEADER_EVT_TXT_PV =  "TSW: table type to roij_txt
*  CT_TICKET_ITEM_EVT_PV =  "Ticket Events Table Type
*  CT_TICKET_ITEM_EVT_TXT_PV =  "TSW: table type to roij_txt

TABLES
   T_ERR_LOG =  "OIL-TSW: Structure for error log for ticketing process
   T_TKT_I_O2 =  "Appendix: TSW Ticket item - Additional Quantities
*  T_OIJNOMSUBITEMS =  "Nomination Sub-Item
   T_REVERSAL_DOCS =  "OIL-TSW: Structure for reversal tickets

EXCEPTIONS
   NO_DOCUMENT_GENERATED = 1
.



IMPORTING Parameters details for OIJ_EL_GTM_TSW_DOCG_REVERSE_TC

I_TICKET_HEADER - Universal ticket table

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

I_TICKET_ITEM - Universal ticket item table

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

I_OIJNOMH - Nomination Header

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

I_OIJNOMI - Nomination Item

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

I_OIJIMPORT - TSW: Parameter imported to CIP functions

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

I_TKT_I_O1 - Appendix: TSW Ticket item - Conversion Parameters

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

CHANGING Parameters details for OIJ_EL_GTM_TSW_DOCG_REVERSE_TC

CT_TICKET_HEADER_EVT - Ticket Events Table Type

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

CT_TICKET_HEADER_EVT_TXT - TSW: table type to roij_txt

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

CT_TICKET_ITEM_EVT - Ticket Events Table Type

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

CT_TICKET_ITEM_EVT_TXT - TSW: table type to roij_txt

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

CT_TICKET_HEADER_EVT_PV - Ticket Events Table Type

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

CT_TICKET_HEADER_EVT_TXT_PV - TSW: table type to roij_txt

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

CT_TICKET_ITEM_EVT_PV - Ticket Events Table Type

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

CT_TICKET_ITEM_EVT_TXT_PV - TSW: table type to roij_txt

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

TABLES Parameters details for OIJ_EL_GTM_TSW_DOCG_REVERSE_TC

T_ERR_LOG - OIL-TSW: Structure for error log for ticketing process

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

T_TKT_I_O2 - Appendix: TSW Ticket item - Additional Quantities

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

T_OIJNOMSUBITEMS - Nomination Sub-Item

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

T_REVERSAL_DOCS - OIL-TSW: Structure for reversal tickets

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

EXCEPTIONS details

NO_DOCUMENT_GENERATED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIJ_EL_GTM_TSW_DOCG_REVERSE_TC 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_err_log  TYPE STANDARD TABLE OF OIJ_EL_ERROR_LOG_STR, "   
lv_i_ticket_header  TYPE OIJ_EL_TICKET_H, "   
lv_ct_ticket_header_evt  TYPE OIJTE_T, "   
lv_no_document_generated  TYPE OIJTE_T, "   
lt_t_tkt_i_o2  TYPE STANDARD TABLE OF OIJ_EL_TKT_I_O2, "   
lv_i_ticket_item  TYPE OIJ_EL_TICKET_I, "   
lv_ct_ticket_header_evt_txt  TYPE OIJ_TXT, "   
lv_i_oijnomh  TYPE OIJNOMH, "   
lt_t_oijnomsubitems  TYPE STANDARD TABLE OF OIJNOMSUBITEMS, "   
lv_ct_ticket_item_evt  TYPE OIJTE_T, "   
lv_i_oijnomi  TYPE OIJNOMI, "   
lt_t_reversal_docs  TYPE STANDARD TABLE OF ROIJREVDOC, "   
lv_ct_ticket_item_evt_txt  TYPE OIJ_TXT, "   
lv_i_oijimport  TYPE ROIJ_EL_IMPORT, "   
lv_ct_ticket_header_evt_pv  TYPE OIJTE_T, "   
lv_i_tkt_i_o1  TYPE OIJ_EL_TKT_I_O1, "   
lv_ct_ticket_header_evt_txt_pv  TYPE OIJ_TXT, "   
lv_ct_ticket_item_evt_pv  TYPE OIJTE_T, "   
lv_ct_ticket_item_evt_txt_pv  TYPE OIJ_TXT. "   

  CALL FUNCTION 'OIJ_EL_GTM_TSW_DOCG_REVERSE_TC'  "CIP FM to reverse Trading Contract
    EXPORTING
         I_TICKET_HEADER = lv_i_ticket_header
         I_TICKET_ITEM = lv_i_ticket_item
         I_OIJNOMH = lv_i_oijnomh
         I_OIJNOMI = lv_i_oijnomi
         I_OIJIMPORT = lv_i_oijimport
         I_TKT_I_O1 = lv_i_tkt_i_o1
    CHANGING
         CT_TICKET_HEADER_EVT = lv_ct_ticket_header_evt
         CT_TICKET_HEADER_EVT_TXT = lv_ct_ticket_header_evt_txt
         CT_TICKET_ITEM_EVT = lv_ct_ticket_item_evt
         CT_TICKET_ITEM_EVT_TXT = lv_ct_ticket_item_evt_txt
         CT_TICKET_HEADER_EVT_PV = lv_ct_ticket_header_evt_pv
         CT_TICKET_HEADER_EVT_TXT_PV = lv_ct_ticket_header_evt_txt_pv
         CT_TICKET_ITEM_EVT_PV = lv_ct_ticket_item_evt_pv
         CT_TICKET_ITEM_EVT_TXT_PV = lv_ct_ticket_item_evt_txt_pv
    TABLES
         T_ERR_LOG = lt_t_err_log
         T_TKT_I_O2 = lt_t_tkt_i_o2
         T_OIJNOMSUBITEMS = lt_t_oijnomsubitems
         T_REVERSAL_DOCS = lt_t_reversal_docs
    EXCEPTIONS
        NO_DOCUMENT_GENERATED = 1
. " OIJ_EL_GTM_TSW_DOCG_REVERSE_TC




ABAP code using 7.40 inline data declarations to call FM OIJ_EL_GTM_TSW_DOCG_REVERSE_TC

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!