Purpose
This report creates test payloads for the Error & Conflict Handler(ECH)and according Orders in the Post Processing Office (PPO). The testdata can be used to test the functionality of the payload editor.

Integration
The payload editor can be started from the PPO:

• /SAPPO/PPO2 (Edit PPO Order)


• /SAPPO/PPO3 (Display PPO Order)

The demo application SFLIGHT and its data is used to create the testdata for the payload editor and PPO. Should problems arise with regardsto the test data please use report SAPBC_DATA_CONSISTENCY_CHECK
to execute a consistency check of the demo data. If necessary,report SAPBC_DATA_GENERATOR generatesthetest data.
If you want to manipulate the data of the payloads and the errors andmessages that occur, you can edit the ECATT test data containerFEH_TEST_SFLIGHT (transaction SECATT).

Prerequisites
The following customizing needs to be maintained before payloads andPPOorders can be created


• ECH Components & Processes under
ECHProccesses:
Component ,,Process,,Action Class,,Persistency Class,,Notification Class
FEH_TEST,,SFLIGHT,,CL_FEHTEST_SFLIGHT_ACTION,,CL_FEH_MESSAGE_PERSISTENCY
,,CL_FEH_REGISTRATION

• PPO Processes under Define Business Processes

:
Software Component,,Process
FEH_TEST,,SFLIGHT

• Mapping between above ECH and PPO under Map
ECH Processes to PPO Processes:
Component,,Process,,Software Component,,PPO Process
FEH_TEST,,SFLIGHT,,FEH_TEST,,SFLIGHT

Selection


• Test: if this flag is set, no payloads are persisted (the GUID that are
returned do not exist). The reports only gives an indication then ifpayloads will be created: if GUID's are displayed, then payloads willbecreated and persisted when you run the report without the test flag.