This chapter provides an overview on the customer functions and change options in processing that affect the interface.

The following modifications are possible:

• You are using standard IDoc TPSSHT01, but you want to process the IDoc according to your own requirements.

• You are using standard IDoc TPSSHT01 but want to influence the standard IDoc processing, i.e. error processing should be modified or IDoc contents should be interpreted according to the customer’s requirements.

• You are using a modified IDoc with your own segments and want to implement a certain processing for the data in these segments.

• You are using a modified IDoc with your own segments and want to process the IDoc according to your own requirements.

• You are using your own IDoc with a new message type and have to process the IDoc according to your own requirements.

The following describes individual modification options.

The framework function module filters out the user data per IDoc and calls up your own processing function module in the application for every IDoc in a loop. All the data are then saved together in the database.

Before and after processing each IDoc and after saving all shipment data a customer function is implemented.

You can use the customer function before processing the IDoc to manipulate data in the IDoc before it is transferred to the application functions. The customer function after IDoc processing allows you to process your own segments.

Customer functions for the transportation planning interface can be found in function group XV56 in the R/3 system with the description ‘EXIT_SAPLV56I_0xx’. You can use transaction SMOD to access enhancements. The names begin with ‘V56I’. The documentation for each function module describes how to use the available customer functions. Activating customer functions takes place in transaction CMOD. Please use the R/3 system online documentation for instructions on using SMOD and

When creating your own function module, you must make sure that you do not set Commit Work, because the function module branches back the ALE service level after processing. This is where application errors are copied, IDoc status set and possibly rollbacks are listed. After Commit Work, a rollback can no longer be carried out if an error occurs. This could lead to partially posted IDocs and therefore to inconsistencies during error processing.

You have to take into account the fact that further I/Os, that occur in the customer functions can reduce performance.

You define your own IDoc segments in IDoc maintenance (WE30). Please see the corresponding documentation for the ALE group.

You define your own IDoc in the same way as for maintaining your own segments. This IDoc must be assigned to a new message type. You must find a partner profile for this message type. The tables for entry to transaction WE42 must be maintained.

You have the following modification options for the individual modification scenarios:

• For IDoc processing, you create your own processing function module, that can be copied from the standard function module and then adjusted as required.

• You activate the customer functions in the standard function module. If you want to influence error processing, you must enhance the customer function after IDoc processing by generating using own error status and then activate. If you want to influence IDoc processing, then you need to activate and use customer function own update.

• You define your own IDoc segments in the standard IDoc and use the customer function for own update, in order to process the data from your own segments.

• You define your own IDoc segments in the standard IDoc and create your own processing function module as in scenario 1.

• You define your own IDoc and create your own processing function module. When creating the function module, you can use the standard help function modules.

The following modification scenarios:

• You use standard IDoc TPSDLS01, but want to change standard processing, i.e. the structure or content of this IDoc.

• You use a modified IDoc with your own segments and want to set your own processing to construct the data from this segment.

• You use a modified IDoc with your own segments and want to process the IDoc structure according to your own requirements.

• You use your own IDoc with a new message type and have to process the IDoc according to your own requirements.

The following section describes the individual modification options.

The formatting for the transmission of IDocs is carried out in the application. The IDoc is constructed, the partner determined and the configurations are made for the ALE layer. The construction of the IDoc is carried out in the application function modules.

This is where you have your first opportunity to carry out modifications by creating your own function modules. To ensure that this is called by the application, you have to link it to the required application menu.

The following function modules from function group V561 are used in the transportation planning interface for constructing and transmitting standard IDocs:

For the outbound function modules for transmission of planning requests, the following customer functions are available, for adding your own IDoc segments and/or changing the standard IDoc construction. The following list displays all available customer functions for outbound processing of planning requests. The function groups and transactions displayed for inbound processing are also valid for customer functions in outbound processing.

As mentioned in inbound processing, you define your own IDoc segments in IDoc maintenance. A customer-specific IDoc can also be defined for outbound processing. Apart from IDoc definition, you only need to maintain the partner profile for outbound processing here.

You have the following modification options for the individual modification scenarios:

• For IDoc processing, you create your own processing function module, that can be copied from the standard function module of the corresponding message type and then adjusted as required.

• You activate the customer functions in the standard function module in order to influence the standard IDoc structure.

• You define your own IDoc segments in the standard IDoc and use the customer exit to fill your own segment with data.

• You define your own IDoc segments in the standard IDoc and create your own function module that can be copied from the standard function module of the corresponding message type and then adjusted as required.