Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Operations not getting created from BAPI_ROUTING_CREATE even though routing is getting generated

01-21-2026 12:07 PM
integration_11 Newcomer
523 views 2 comments
0 Likes
SAP Managed Tags
Subscribe

Hi All,

I am calling BAPI to create routing as shown below and passing the following data. The routing is getting created without any errors, but operations are not getting created. Can someone please suggest how this can be fixed. The same data when passed from SE37, operations are getting created.

P.S: I have already tried leading 0's in sequence, group counter, activity.

CALL FUNCTION 'BAPI_ROUTING_CREATE'
      EXPORTING
        testrun                = lv_testrun
*        profile                = 'PI01'
        bomusage               = '1'
        application            = 'PP01'
      IMPORTING
        group                  = lv_group
        groupcounter           = lv_groupcounter
      TABLES
        task                   = lt_tsk
        materialtaskallocation = lt_mtk
        sequence               = lt_seq
        operation              = lt_opr
        suboperation           = lt_sbo
        referenceoperation     = lt_rfo
        workcenterreference    = lt_wcr
        componentallocation    = lt_com
        productionresource     = lt_prt
        inspcharacteristic     = lt_cha
        textallocation         = lt_txt
*       text                   = text[]
        return                 = lt_return[]
      EXCEPTIONS
        error_message          = 1
        OTHERS                 = 2.


    LOOP AT lt_return WHERE type CA 'EAX'. ENDLOOP.

    IF sy-subrc IS INITIAL.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' EXPORTING wait = 'X'.
    ENDIF.

BAPI FieldTASK_LIST_GROUPGROUP_COUNTERCHANGE_NOVALID_FROMCHANGE_NO_TOVALID_TO_DATEDEL_INDTASK_LIST_USAGEPLANTTASK_LIST_STATUSTASK_MEASURE_UNITTASK_MEASURE_UNIT_ISOLOT_SIZE_FROMLOT_SIZE_TORESP_PLANNER_GROUPDESCRIPTIONOLD_NUMBER_OF_TASK_LISTRECALC_STD_VALUESDYN_MODIF_LEVELDYN_MODIF_RULEDYN_MODIF_BY_VENDORDYN_MODIF_BY_MANUFACTDYN_MODIF_BY_CUSTOMRSAMPLE_DRAWING_PROCEDUREIND_UNITS_EXT_NUMBERINGIDENT_KEYINSPPOINT_PARTIALLOT_ASSGNMTCHANGE_RULEOBJECT_CHANGE_TYPEPLANNING_WORK_CENTER
 500000611 20260113 99991231 1PE014KG 1999999999 SFG005 TEST             

 

 

MATERIALPLANTTASK_LIST_GROUPGROUP_COUNTERCHANGE_NOVALID_FROMCHANGE_NO_TOVALID_TO_DATEDEL_INDDOC_NUMBERITM_NUMBERWORK_BREAKDOWN_STRUCT_ELEMENTMATERIAL_EXTERNALMATERIAL_GUIDMATERIAL_VERSION
SFG05PE01500000611 20260113 99991231  0 SFG05 

 

 

TASK_LIST_GROUPGROUP_COUNTERSEQUENCE_NOCHANGE_NOVALID_FROMCHANGE_NO_TOVALID_TO_DATEDEL_INDACTIVITYOPERATION_IDCONTROL_KEYOBJ_IDOBJECT_TYPE_CIM_RESOURCEWORK_CNTRPLANTSTANDARD_TEXT_KEYDESCRIPTIONOPERATION_MEASURE_UNITOPERATION_MEASURE_UNIT_ISODENOMINATORNOMINATORBASE_QUANTITYBREAK_TIMEBREAK_UNITBREAK_UNIT_ISOACTTYPE_01STD_UNIT_01STD_UNIT_01_ISOSTD_VALUE_01ACTTYPE_02STD_UNIT_02STD_UNIT_02_ISOSTD_VALUE_02ACTTYPE_03STD_UNIT_03STD_UNIT_03_ISOSTD_VALUE_03ACTTYPE_04STD_UNIT_04STD_UNIT_04_ISOSTD_VALUE_04ACTTYPE_05STD_UNIT_05STD_UNIT_05_ISOSTD_VALUE_05ACTTYPE_06STD_UNIT_06STD_UNIT_06_ISOSTD_VALUE_06STD_VALUE_CALCULATION_TYPESTD_VALUE_YEAR_OF_CALCULATIONSTD_VALUE_CODE_REFERENCE_NOSTD_VALUE_CALCULATION_BASISNO_OF_CONFIRMATION_SLIPSNO_OF_TIME_TICKETSWAGETYPESUITABILITYNO_OF_EMPLOYEESETUP_GROUP_CATEGORYSETUP_GROUP_KEYSETUP_TYPE_KEYSCRAP_FACTORWAGEGROUPREQUIRED_OVERLAPPINGOPTIONAL_OVERLAPPINGIND_CONT_FLOW_PRODUCTIONMIN_OVERLAP_TIME_UNITMIN_OVERLAP_TIME_UNIT_ISOMIN_OVERLAP_TIMEMIN_SEND_AHEAD_QTYIND_SPLITTING_REQRDMAX_NO_OF_SPLITSMIN_PROCESSING_TIME_UNITMIN_PROCESSING_TIME_UNIT_ISOMIN_PROCESSING_TIMEMAX_WAIT_TIME_UNITMAX_WAIT_TIME_UNIT_ISOMAX_WAIT_TIMEREQUIRED_WAIT_TIME_UNITREQUIRED_WAIT_TIME_UNIT_ISOREQUIRED_WAIT_TIMESTANDARD_QUEUE_TIME_UNITSTANDARD_QUEUE_TIME_UNIT_ISOSTANDARD_QUEUE_TIMEMIN_QUEUE_TIME_UNITMIN_QUEUE_TIME_UNIT_ISOMIN_QUEUE_TIMESTANDARD_MOVE_TIME_UNITSTANDARD_MOVE_TIME_UNIT_ISOSTANDARD_MOVE_TIMEMIN_MOVE_TIME_UNITMIN_MOVE_TIME_UNIT_ISOMIN_MOVE_TIMETEARDOWN_AND_WAIT_INDREDUCTION_STRATEGYSORTED_BYVENDOR_NOPLND_DELRYINFO_REC_NET_PRICEPRICE_UNITCOST_ELEMCURRENCYCURRENCY_ISOINFO_RECPURCH_ORGPURCH_GROUPFIXED_LOT_EXT_PROCESS_INDMATL_GROUPUSERFIELDS_KEYWORD_IDUSERFIELD_CH20_00USERFIELD_CH20_01USERFIELD_CH10_02USERFIELD_CH10_03USERFIELD_QUAN_04USERFIELD_UNIT_04USERFIELD_UNIT_04_ISOUSERFIELD_QUAN_05USERFIELD_UNIT_05USERFIELD_UNIT_05_ISOUSERFIELD_CURR_06USERFIELD_CURRENCY_06USERFIELD_CURRENCY_06_ISOUSERFIELD_CURR_07USERFIELD_CURRENCY_07USERFIELD_CURRENCY_07_ISOUSERFIELD_DATE_08USERFIELD_DATE_09USERFIELD_FLAG_10USERFIELD_FLAG_11COST_RELEVANTPO_NUMBERPO_ITEMCO_BUSPROCCUMULATION_TYPESUB_ACT_NOT_IN_ORDER_INDEXT_PROC_WITH_SUBCONTRACT_INDINSPTYPERECORDING_VIEWFREE_GRIDTIME_GRIDQUANT_GRIDQUANTONCETIME_UNITTIME_UNIT_ISOTIME_FACTORQTY_BTW_TWO_INSPECTIONSQUANT_UNITQUANT_UNIT_ISOSTOCK_RELATED_PARTIAL_LOT_ASSGINSP_POINT_COMPLT_FLOW_VARIANTGROUP_OPERATION
5000006110 20260113 99991231 10 PP01  FW_01PE01 TEST RUN1KG 115      10.000   51.000                                                                                                                      
5000006110 20260113 99991231 20 PP01  FW_01PE01 TEST RUN22KG 115      12.000   55.000                                                                                                                      
0 Likes

Know the answer?

Help others by sharing your knowledge.

Answer

Need more details?

Request clarification before answering.

Show replies
Show replies
IreneLiu
Product and Topic Expert
Product and Topic Expert
‎2026 May 28 2:01 AM
0 Likes
Based on your question, I have adjusted tags for better searchability. You may find details for using tags in Blog below: https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/q-amp-a-for-sap-s-4hana-cloud...

Accepted Solutions (0)

Answers (1)

Answers (1)

HenrikeGroetecke
Product and Topic Expert
Product and Topic Expert
‎2026 Feb 23 3:56 PM
0 Likes

Hello,

Thank you very much for your question. I'm very sorry for the delay.

In this case, I asked an internal chatbot for support. Here's the response:

To resolve the issue where operations are not getting created when using the BAPI ‘BAPI_ROUTING_CREATE’, you should ensure that the data being passed is complete and correctly formatted. Here are a few steps to consider:

  1. Check Mandatory Fields: Ensure that all mandatory fields for operations are filled correctly. This includes fields like ACTIVITY, OPERATION_ID, CONTROL_KEY, WORK_CNTR, and PLANT.

  2. Sequence and Group Counter: Verify that the SEQUENCE_NO and GROUP_COUNTER are correctly formatted and match the expected format in the system. Leading zeros might be necessary depending on the system configuration.

  3. Data Consistency: Ensure that the data in lt_opr (operations table) is consistent with the data in lt_tsk (task list table) and lt_seq (sequence table). The TASK_LIST_GROUP and GROUP_COUNTER should match across these tables.

  4. Test in SE37: Since the data works in SE37, compare the data being passed in the BAPI call with the data used in SE37 to identify any discrepancies.

  5. Check for Errors: After the BAPI call, check the lt_return table for any error messages that might indicate why the operations are not being created.

  6. Transaction Commit: Ensure that the BAPI transaction is committed correctly using BAPI_TRANSACTION_COMMIT after the BAPI call.

I hope this helps. 

Kind regards,

Henrike

Show replies
Show replies
Ask a Question