SAP /SAPAPO/SEQ_API_SYNCHRONIZE Function Module for Sequencing: Takt-Based Scheduling with Actual Data Comparison









/SAPAPO/SEQ_API_SYNCHRONIZE is a standard /sapapo/seq api synchronize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sequencing: Takt-Based Scheduling with Actual Data Comparison 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/seq api synchronize FM, simply by entering the name /SAPAPO/SEQ_API_SYNCHRONIZE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SAPAPO/SEQ_API
Program Name: /SAPAPO/SAPLSEQ_API
Main Program: /SAPAPO/SAPLSEQ_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function /SAPAPO/SEQ_API_SYNCHRONIZE 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/SEQ_API_SYNCHRONIZE'"Sequencing: Takt-Based Scheduling with Actual Data Comparison
  EXPORTING
*  IV_SIMVERSION = '000' "Name der Planversion
*  IV_SIMSESSION =  "GUID zur Identifikation transaktionale Simulations-Session
   IV_IPPE_LINE_NAME =  "Bezeichnung iPPE-Knoten
   IV_SCHEDULE_START =  "UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)
   IV_SCHEDULE_END =  "UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)
*  IV_COMMIT_WORK = 'X' "Dummy Datenlement für Boolean-Felder
*  IV_SHOWLOG = 'X' "Dummy Datenlement für Boolean-Felder
*  IV_RUN_RPM = 'X' "Dummy Datenlement für Boolean-Felder

TABLES
*  ET_RETURN =  "Returnparameter
.



IMPORTING Parameters details for /SAPAPO/SEQ_API_SYNCHRONIZE

IV_SIMVERSION - Name der Planversion

Data type: /SAPAPO/VRSIOID
Default: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SIMSESSION - GUID zur Identifikation transaktionale Simulations-Session

Data type: /SAPAPO/OM_SIMSESSION
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_IPPE_LINE_NAME - Bezeichnung iPPE-Knoten

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

IV_SCHEDULE_START - UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

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

IV_SCHEDULE_END - UTC-Zeitstempel in Kurzform (JJJJMMTThhmmss)

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

IV_COMMIT_WORK - Dummy Datenlement für Boolean-Felder

Data type: /SAPAPO/BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SHOWLOG - Dummy Datenlement für Boolean-Felder

Data type: /SAPAPO/BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_RUN_RPM - Dummy Datenlement für Boolean-Felder

Data type: /SAPAPO/BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for /SAPAPO/SEQ_API_SYNCHRONIZE

ET_RETURN - Returnparameter

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

Copy and paste ABAP code example for /SAPAPO/SEQ_API_SYNCHRONIZE 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_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_simversion  TYPE /SAPAPO/VRSIOID, "   '000'
lv_iv_simsession  TYPE /SAPAPO/OM_SIMSESSION, "   
lv_iv_ippe_line_name  TYPE PVS_PNODE, "   
lv_iv_schedule_start  TYPE TIMESTAMP, "   
lv_iv_schedule_end  TYPE TIMESTAMP, "   
lv_iv_commit_work  TYPE /SAPAPO/BOOLEAN, "   'X'
lv_iv_showlog  TYPE /SAPAPO/BOOLEAN, "   'X'
lv_iv_run_rpm  TYPE /SAPAPO/BOOLEAN. "   'X'

  CALL FUNCTION '/SAPAPO/SEQ_API_SYNCHRONIZE'  "Sequencing: Takt-Based Scheduling with Actual Data Comparison
    EXPORTING
         IV_SIMVERSION = lv_iv_simversion
         IV_SIMSESSION = lv_iv_simsession
         IV_IPPE_LINE_NAME = lv_iv_ippe_line_name
         IV_SCHEDULE_START = lv_iv_schedule_start
         IV_SCHEDULE_END = lv_iv_schedule_end
         IV_COMMIT_WORK = lv_iv_commit_work
         IV_SHOWLOG = lv_iv_showlog
         IV_RUN_RPM = lv_iv_run_rpm
    TABLES
         ET_RETURN = lt_et_return
. " /SAPAPO/SEQ_API_SYNCHRONIZE




ABAP code using 7.40 inline data declarations to call FM /SAPAPO/SEQ_API_SYNCHRONIZE

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_simversion) = '000'.
 
 
 
 
 
DATA(ld_iv_commit_work) = 'X'.
 
DATA(ld_iv_showlog) = 'X'.
 
DATA(ld_iv_run_rpm) = 'X'.
 


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!