/nse38/Handling Errors SchedAgrs
App type: SAP GUI
Description:  Special features for delivery schedules allow you to define for each sold-to party or combination of sold-to party/unloading point how delivery schedules are to be processed. The system checks this record in Customizing for every incoming delivery schedule. If it cannot find a record for the particular sold-to party, it issues an error message and ends processing of the IDoc. 
Key features:    Enter a message version Using a version, you can designate how the system should react to errors during checks on the incoming delivery schedules of a particular sold-to party. You can set the system to issue a warning message, an error message, or no message at all. You can also, for example, set all the messages to be issued as errors. Note that in the standard system, all variable messages are issued as warnings. There are no preset version numbers in the standard system. You can maintain new ones by choosing Sales  Sales  Documents   Define variable messages. Here, you can assign message types different from those in the standard system to individual messages. Example Opel: Version 01    Message 071 (message type: error) Autos Inc.: Version 02   Message 071 (message type: none) In this example, version 01 has been defined for Opel and contains message 071: “Check item X, quantity change exceeds the change tolerance”. This message has been designated as an error message.Version 02 has been defined for Autos Inc. Since the customer does not attach much importance to tolerance levels, no message category has been assigned to message 071. If the system determines that a tolerance level has been exceeded, no message will be issued.   Activate a special rule for an automobile manufacturer You can use this field to refer to any of the various user exits that you program for EDI processing. The system will then take the user exits into account when processing delivery schedules for the automobile manufacturer that you designate. Example An automobile manufacturer sends material numbers in just-in-time (JIT) delivery schedules in a different format than in forecast delivery schedules. You program a user exit to convert the format of material numbers sent in JIT delivery schedules to match that in forecast delivery schedules.   Enter a delivery prefix for the customer delivery number Customers often use only a portion of your internal delivery number for their records, usually the last few digits. When they send this number in a delivery schedule, the system adds to it the prefix that you have entered here to find the internal delivery number. The system uses the last internal delivery to check self-billing documents. Or you can manually call up the last delivery to check or recalculate cumulative quantities.   Specify whether the system should use the customer purchase order number or unloading point sent in the delivery schedule to find the related sales scheduling agreement   Specify how data on packaging material sent in a delivery schedule should be handled You can set the system to:   Automatically send a mail informing the employee responsible that packaging data is available for processing   Send a mail, and copy the data as text into the sales scheduling agreement   Ignore packaging data altogether   Copy data into the sales scheduling agreement with no mail     Specify whether an employee should be notified if general texts are sent in a delivery schedule   Activate test runs for delivery schedules When you set this indicator, the system does not automatically process an incoming delivery schedule. It sends the employee responsible a mail and the IDoc must then be processed manually.