Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-ADM (Application Component) Additionals Management⤷
WCE1 (Package) IS-R: Labeling (Customizing)
IMG Activity
| ID | W_DF_LT_0201 | Procedure for Additionals |
| Transaction Code | S_ALR_87003711 | IMG Activity: W_DF_LT_0201 |
| Created on | 19981222 | |
| Customizing Attributes | W_DF_LT_0201 | Procedure for additionals |
| Customizing Activity | W_DF_LT_0201 | Procedure for additionals |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_DF_LT_0201 |
In this step you define procedures for additionals.
On the initial screen you make general settings; on the detail screen you make settings for the applications for purchase orders, goods movements, deliveries or sales orders applications.
In the column "Enter additional", you check the box to indicate whether an additional is to be entered for the procedure. This box should normally be checked.
You can, however, also use procedures for additionals to transfer texts that have been created as supplementary information without reference to a particular additional. In this case, you should not check the box.
Select a procedure for additional and define the application for which a follow-up action should be triggered.
Depending on the application, you can define the parameters required for a follow-up action to trigger an additional:
- In the case of purchase orders, you can differentiate using order type and category. The system can also check if the procedure for additional has been assigned to the current vendor. This assignment guarantees that a vendor only executes the activities which he is authorized to execute. In vendor price marking, only the vendor who attaches labels to merchandise receives information about relevant additionals.
- In the case of goods movements, you differentiate by movement type.
- In the case of deliveries, you can define the delivery type for which a follow-up action is triggered.
- Sales document categories and sales document types are used in analysis. The system can execute a search to find the internal procedure for additional defined by the customer if the indicator is flagged.
If a procedure for additional is to be valid for all parameter values, you can enter an asterisk (*) in the field. For example, if a procedure is valid for document category F (purchase order) and all order types, enter '*' as the value for the order type.
If more parameters are necessary for analysis, the relevant structures in table TWTCTRL must be modified.
If an additional is only to be affixed in particular plants, you have to enter the relevant class and plant in the fields "class type"
and "class".
A class is read directly from the classification system at the time of the event, i.e. the elements in a class are not fixed. If on day "t" a goods receipt in a distribution center results in an additionals IDoc being created for a particular class, this IDoc can differ from that created on day "t+x", because the class on day "t" may contain different plants than on day "t+x".
If the application is allowed on account of the movement type in any plant, no entry has to be made here.
You should select one of the following follow-up actions in the first step:
Code Description
<space> Information only
1 Generate additionals IDoc immediately
2 Generate PO for additional
3 Wait for additional IDoc to be requested externally
8 Generate additional IDoc from delivery output
85 SLS: pre-packing
98 Generate additionals IDoc in the transport order
99 Generate additionals IDoc immediately (before posting; CAUTION!)
Follow-up actions leading to entries in info structure S108 of the RIS are configured in the second step for existing procedures for additionals.
Examples
The following considerations are useful for deriving the required procedures for additionals:
- Which applications must react to additionals? Is the assortment list enough information for stores? Should additionals (for example, tickets) be attached to the goods in the distribution center by your own company? Do you require your own additionals management for ordering additionals?
- Should relevant changes be analyzed centrally for certain additionals? Could this be the case for printing promotional posters, for example?
- Do you want the sender to be narrowed down to a plant class because when stock is transferred in two steps between two distribution centers a goods receipt is posted but the additionals are attached in only one of the distribution centers?
- Are additionals included so that they can function as a Supplementary Logistics Service?
Requirements
If you want to use special additionals in a distribution chain for some groups of plants, you have to use the classification system.
You have to set up the necessary classes and assign plants to them.
Standard settings
The standard system contains seven procedures for additionals. Procedures 0001 and 0002 refer to additionals management. Procedure 0003 shows how an additionals IDoc is generated based on a goods receipt. Procedure 0004 is used to inform stores about additionals to which the procedure for additional is assigned.
Procedures 0005 and 0006 show how procedures for additionals can be set as Supplementary Logistics Services for procurement and deliveries.
Procedure 0007 shows settings for sales order processing. The additionals from the referenced sales and distribution document are used for deliveries.
These procedures can be copied and used as a reference for your own procedures. You can give your own procedure a name. As soon as you have created your own procedures for additionals, you should delete the standard ones.
The entry in the standard system for "class type" and "class" is empty. It contains no classes.
Effects:
- Procedure 0001: Additionals ordered in company
When a standard purchase order (order category F, order type NB) is created or changed, an additionals document is updated. An additionals purchase order can then be generated for this document. - Procedure 0002: IDoc request via BAPI
When a standard purchase order is created or changed, an additionals document is updated with the status "IDoc request not yet executed". As soon as the IDoc is requested by the recipient, the status changes to "IDoc requested by BAPI". - Procedure 0003: Additional affixed in DC at goods receipt
An additionals IDoc is generated when a goods movement is posted if the movement type is 101 (goods receipt) or 501 (goods receipt without purchase order reference). - Procedure 0004: Additional affixed in store
This procedure is assigned to additionals that are to be printed centrally, for example, promotional posters.
The fields "Assortment list" and "Created centrally" are selected. No entries are defined in the control tables for the procedures for additionals. The assortment list is used to inform the stores of the procedures involved. The ADDIREL field is not selected in segment E1WTADAL1 of the assortment list IDoc.
Changes to materials to which an additional is assigned can be used to create a central IDoc using procedure 0004. To do this, report ADDI_ANALYSIS_OF_CHANGES (transaction WTCA) must be executed when the system is running. - Procedure 0005: SLS: Pre-packing, procurement
- Define additionals as a Supplementary Logistics Service in merchandise distribution. Relevant data about pre-packing to be done by the vendor is transferred. The settings made here are used for external purchase orders to vendors to generate subitems for end recipients.
- Procedure 0006: SLS: Pre-packing, deliveries
Vendors use additionals in sales orders and deliveries to process SLS data provided by the sold-to party. The service data is assigned to the additional using procedure 0006. - Procedure 0007: Additionals in sales order processing
This procedure is used to pull data from material master data or to copy data from preceding documents when quotations are requested or made, and when an order is placed. In sales order processing, an additionals IDoc is generated when an outbound delivery for a sales order is created.
Class types 035 and 030 have been defined for additionals in the Customizing settings for control tables.
Recommendation
For the sake of clarity, the number of procedures should be limited.
If you have more than 10 different procedures, you should group them together.
If no class is maintained in material maintenance, the additionals IDoc is valid for all plants in which the material is listed. This is also relevant for the procedure for additionals. If no class has been entered in the control table, the procedure for additionals is valid for every plant.
Also, it is not necessary to create any sort of "higher-level class" containing all your plants.
Activities
Define procedures for additionals.
Further notes
All areas of a company affected by a procedure for additionals and their partners must be informed of the effects of the procedure.
A printer connection to print labels from SAPscript, for example, has not been planned. You can print labels and other materials using an&#
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | W_DF_LT_0201 | 0 | I020004207 | Additionals Management |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_TWTFM | C - View cluster | SM34 | 00000001 | Maintain the procedure for additionals |
History
| Last changed by/on | SAP | 19990422 |
| SAP Release Created in |
