Consider the example as below:

In the API there are no fields with defined time labels such as Setup time or processing time. Instead, the API uses the following fields to map the time, unit of measure for the time, activity type.

For BAPI_ROUTING_CREATE

STD_VALUE_xx should be the value of appropriate time based on the above table. For example, if work center is 1000 inside plant 1100 then STD_VALUE_01 is setup time and STD_UNIT_01 is the unit of measure for setup time.

If activity type is customized from Windchill then that also can be mapped to ACTTYPE_01.

For /PTC/ZRFC_MODIFY_ROUTING

STANDARD_VALUE x should be the value of appropriate time based on the above table. For example,. if work center is 1000 inside plant 1100 then STANDARD_VALUE2 is the setup time and UOM_FOR_STANDARDVALUE1 is the unit of measure for setup time.

If activity type is customized from Windchill then that also can be mapped to ACTIVITY_TYPE1.

Default mapping maps Collection to CBO and CBO to SAP as follows:

For the above times the customization can be done as below:

1) For inserting/updating operations while creating Process plans.

The original table, now populated as below:

If you have a customized field that needs to map to Production time for work-center/plant 1300/1200, then it could have been mapped as shown below:

The above mappings are required to be done at following places.

Process Name: ProcessDefinitions/ERP Communication/Routing/Start_CBORouting_SAPCreate_PD Activity: Invoke_BAPI_ROUTING_CREATE

Input mapping in the activity: Operation, sub-operation

2) For insertion/updating of operations while updating of process plans.

The original table, now populated as shown below:

Process Name: ProcessDefinitions/ERP Communication/Routing/Start_CBORouting_SAPChange_PD

Activity: Invoke_ZRFC_MODIFY_ROUTING

Input mapping in the activity: T_OPERATION_INSERT, T_OPERATION_MODIFY, T_SUBOPERATION_INSERT, T_SUBOPERATION_MODIFY

Changes in /PTC/ZRFC_MODIFY_ROUTING: By default BDC recording takes all the fields listed below on the screen as per the OOTB workcenter details that used for recording BDC. But for other workcenters it might not have all the fields available. In this case /PTC/ZRFC_MODIFY_ROUTING will return an error like “filed and field does not exist on screen.”. The /PTC/ZRFC_MODIFY_ROUTING needs to be customized to fill in the values in the fields shown below, as if they existed on the screen.

By default code maps are:

Work-center details that are used for OOTB BDC recording: