This section 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 method, (error processing are to be modified or IDoc contents are to be interpreted according to the customer’s requirements, for example).

• 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 need 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 data is then saved together in the database.

A customer function is implemented before and after processing each IDoc and after saving all shipment data.

You can use the customer function before processing the IDoc to manipulate data in the IDoc before it is transferred to the application functions. After IDoc processing, the customer function 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. Consult the R/3 System online documentation for instructions on how to use SMOD and CMOD.

When creating your own function module or using customer functions, you must make sure that you do not set Commit work, because the function module branches back into the ALE service level after processing. Application errors are copied, IDoc status is set and rollbacks may be listed in the ALE service level. 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.

Keep in mind that further I/Os that occur in the customer functions can reduce performance.

You can define your own IDoc segments in IDoc maintenance (WE30). Refer to the corresponding documentation for the ALE group.

You can define your own IDoc the same way you maintain your own segments. This IDoc needs to be assigned to a new output type. For this output type, you must set a partner profile. You must also maintain the tables for entry in transaction WE42.

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

• For IDoc processing, you can create your own processing function module, which can be copied from the standard function module and then adjusted, if necessary.

• You can activate the customer functions in the standard function module. If you want to change error processing, you must enhance the customer function after IDoc processing by adding Own error status and then activating it. If you want to modify IDoc processing, then you need to activate and use customer function Own update.

• You can 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 can define your own IDoc segments in the standard IDoc and create your own processing function module as in scenario 1.

• You can 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 modifications are possible:

• You are using standard IDoc TPSDLS01, but want to change standard processing (the structure or content of this IDoc, for example).

• You are using a modified IDoc with your own segments and want to set your own processing to assemble 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 are using your own IDoc with a new message type and need to process the IDoc according to your own requirements.

The following describes individual modification options.

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

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

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 can create your own processing function module, which can be copied from the standard function module and then adjusted, if necessary.

• You can activate the customer function in the standard function module in order to change the standard IDoc structure.

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

• You can 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.