SAP /SAPAPO/SEQM_SHIFT_REQ Function Module for Shift Initial Run of Requirements Through the Network
/SAPAPO/SEQM_SHIFT_REQ is a standard /sapapo/seqm shift req SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Shift Initial Run of Requirements Through the Network 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 /sapapo/seqm shift req FM, simply by entering the name /SAPAPO/SEQM_SHIFT_REQ into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SAPAPO/SEQ_MODELMIX_02
Program Name: /SAPAPO/SAPLSEQ_MODELMIX_02
Main Program: /SAPAPO/SAPLSEQ_MODELMIX_02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /SAPAPO/SEQM_SHIFT_REQ 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 '/SAPAPO/SEQM_SHIFT_REQ'"Shift Initial Run of Requirements Through the Network.
EXPORTING
IV_SIMID = "Planversion (operativ oder eine Simulationsversion)
IV_SIMSESSION = "GUID zur Identifikation transaktionale Simulations-Session
* IV_FROM_PLNG_SGMT = GC_TRUE "boolsche Variable (X=true, -=false, space=unknown)
IS_FACTORY = "
IT_MATLOC = "MatLoc + Bewertung + Fertigungsversionen
IT_IO_REQ = "Tabelle mit PP-Daten von Input-/ Output-Knoten
* IS_OPTHORIZ = "
IMPORTING
ET_IO_SHIREQ = "Tabelle mit Daten der Input-/ Output-Knoten einer PegArea
IMPORTING Parameters details for /SAPAPO/SEQM_SHIFT_REQ
IV_SIMID - Planversion (operativ oder eine Simulationsversion)
Data type: /SAPAPO/VRSIOIDOptional: No
Call by Reference: Yes
IV_SIMSESSION - GUID zur Identifikation transaktionale Simulations-Session
Data type: /SAPAPO/OM_SIMSESSIONOptional: No
Call by Reference: Yes
IV_FROM_PLNG_SGMT - boolsche Variable (X=true, -=false, space=unknown)
Data type: BOOLEANDefault: GC_TRUE
Optional: Yes
Call by Reference: Yes
IS_FACTORY -
Data type: PXAPO_MMP_FACTORYOptional: No
Call by Reference: Yes
IT_MATLOC - MatLoc + Bewertung + Fertigungsversionen
Data type: /SAPAPO/SEQ_MATLOC_TABOptional: No
Call by Reference: Yes
IT_IO_REQ - Tabelle mit PP-Daten von Input-/ Output-Knoten
Data type: /SAPAPO/OM_IO_PP_TABOptional: No
Call by Reference: Yes
IS_OPTHORIZ -
Data type: /SAPAPO/SEQ_OPTHORIZ_STROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for /SAPAPO/SEQM_SHIFT_REQ
ET_IO_SHIREQ - Tabelle mit Daten der Input-/ Output-Knoten einer PegArea
Data type: /SAPAPO/OM_IO_PP_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /SAPAPO/SEQM_SHIFT_REQ 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: | ||||
| lv_iv_simid | TYPE /SAPAPO/VRSIOID, " | |||
| lv_et_io_shireq | TYPE /SAPAPO/OM_IO_PP_TAB, " | |||
| lv_iv_simsession | TYPE /SAPAPO/OM_SIMSESSION, " | |||
| lv_iv_from_plng_sgmt | TYPE BOOLEAN, " GC_TRUE | |||
| lv_is_factory | TYPE PXAPO_MMP_FACTORY, " | |||
| lv_it_matloc | TYPE /SAPAPO/SEQ_MATLOC_TAB, " | |||
| lv_it_io_req | TYPE /SAPAPO/OM_IO_PP_TAB, " | |||
| lv_is_opthoriz | TYPE /SAPAPO/SEQ_OPTHORIZ_STR. " |
|   CALL FUNCTION '/SAPAPO/SEQM_SHIFT_REQ' "Shift Initial Run of Requirements Through the Network |
| EXPORTING | ||
| IV_SIMID | = lv_iv_simid | |
| IV_SIMSESSION | = lv_iv_simsession | |
| IV_FROM_PLNG_SGMT | = lv_iv_from_plng_sgmt | |
| IS_FACTORY | = lv_is_factory | |
| IT_MATLOC | = lv_it_matloc | |
| IT_IO_REQ | = lv_it_io_req | |
| IS_OPTHORIZ | = lv_is_opthoriz | |
| IMPORTING | ||
| ET_IO_SHIREQ | = lv_et_io_shireq | |
| . " /SAPAPO/SEQM_SHIFT_REQ | ||
ABAP code using 7.40 inline data declarations to call FM /SAPAPO/SEQM_SHIFT_REQ
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.| DATA(ld_iv_from_plng_sgmt) | = GC_TRUE. | |||
Search for further information about these or an SAP related objects