EXIT_RNC301U2_001 -

General Data in Customer Master   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

This enhancement can be implemented for EDI data exchange in the IS-H System.

You require this enhancement component if you want to make restrictions to the standard processing ofEDI messages in the outbound worklist. In this way, you can, for example, assign only the messages for selected cases or patients to particular processing agents.

You can also implement general processing exclusions. For example, you can make the processing of messages dependent on their age or status.

The following applies to all modifications:

After this user exit, only the messages contained in transfer table INC301S are displayed for processing.

To maintain the same filtering in the outbound and inbound worklist, you have to implement the two components in the same way. Note the additional interface table for the inbound worklist component (program RNC301I2).

Make sure that your implementation doesn't totally exclude messages so that they are not assigned toany processing agents. This can happen all too easily, but isn't simple to detect. These messages wouldthen remain unprocessed. You should bear this in mind especially with regard to programming on actual objects (organizational units, for example) that can change.

It is not recommended to directly program on user IDs. Instead, make use of the option of defining userparameters (transaction SM30, maintain table TPARA), and only program on specific values for these parameters.Thus new assignments are made possible by simply changing the value of the user parameter. The parametervalues should somehow reflect the criteria that are used for the assignment (for example, for letterranges, the parameter should take on the values 'A_K' and 'L_Z' and not '1' and '2'). Mnemonic values simplify program maintenance and in this case the actual assignment too.

If in doubt, ask the advice of experts. The principle is often quickly implemented and you can then easily modify or enhance it.

Please see the sample source code provided and the documentation on the components.


BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.


Length: 2098 Date: 20120526 Time: 163207     triton ( 117 ms )