Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-MDS-AL (Application Component) Allocation⤷
WCA3 (Package) IS-R: Allocation table (Customizing)
IMG Activity
| ID | W_ZF_VK_0611 | Rcpt. determin. |
| Transaction Code | S_AL0_96000282 | (empty) |
| Created on | 20011017 | |
| Customizing Attributes | W_ZF_VK_0611 | Rcpt. determin. |
| Customizing Activity | W_ZF_VK_0611 | Rcpt. determin. |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_ZF_VK_0611 |
Use
The standard program logic for stock allocation provides you with the following options for assigning the recipient to a material involved in stock allocation:
- Manual entry
- Plant/recipient group (maintained in the classification system)
- Allocation rule
Using the new functionality for recipient determination, you can include more complex selections with customer-defined function modules for customer-specific recipient determination (for example, sales area > 500 m², sales > 10,000).
The recipient determination is called for each item and returns the recipient that should be used for the distribution of the item or material concerned.
In the dialog boxes for creating and changing an allocation table, the recipient determination appears as a 'number' representing a particular procedure for selecting the recipient.
You must create the recipient determination in Customizing first and link it with a selection program (an ABAP function module).
You can assign, select and process values for this number using Customizing.
By way of example, this process has been used in function module 'WEMF_WERKE_ZUR_REGION_LESEN' that is delivered with the standard system.
Once you have entered the 'recipient determination number' in the allocation table dialog box, the selection program that was assigned in Customizing is started and it returns the goods recipient to the application program.
The recipient determination is then called if a new item is created in the allocation table or if the 'recipient determination number' is changed for an existing item. To call the recipient determination explicitly, you can use either the menu or a pushbutton in the application toolbar. As the database structures of the allocation table have to have a plant/recipient group, you must create a 'dummy plant/recipient group' after you have called the recipient determination. This plant/recipient group is not stored in the classification system. It is only in the allocation table. The recipients are in the dummy plant/recipient group. These dummy plant/recipient groups are created automatically in the allocation table if you enter the recipients manually.
The ABAP function modules have to have a fixed, predefined interface (see below for detailed description). You can access all sorts of data in the function module (files, databases, Excel sheets). You can also query any conditions and link them with one another. For example, you can process a dialog box for a query on other data.
Requirements
Interface
The function modules must have the following interfaces:
*"*"Lcal interface:
*" IMPORTING
*" VALUE(IM_AUKO) LIKE RW00A STRUCTURE RW00A
*" VALUE(IM_AUPO) LIKE RW01A STRUCTURE RW01A
*" TABLES
*" IM_AULW STRUCTURE RW14A
*" EX_SHIP_TO_PARTY STRUCTURE RAT_SHIP_TO_PARTY
*" EX_MESSG STRUCTURE RW17A
Explanations for the interface
The parameter names indicate whether it is an input parameter (IM_...) or an output parameter (EX_...). You cannot make any changes to the input parameter in the function module through the allocation program that is called.
Parameter IM_AUKO contains the header data of the allocation table.
Parameter IM_AUPO contains the item data of the allocation table and the material and 'recipient determination number' (that you entered previously or that was copied to the item from the allocation table type).
Table IM_AULW contains the default delivery dates of the allocation table and of the allocation item (if the delivery dates were entered previously). As several delivery dates are generally possible (split delivery), the delivery dates are transferred in table format. Only the default delivery dates can be transferred, as the exact delivery dates (to the exact day of the week) are not yet defined at this stage.
Table EX_SHIP_TO_PARTY contains the (10-character) customer number of all the recipients that were determined in the function module. The recipient's customer number must always be filled. An option for plants is to have the (4-character) plant number returned. However, if the customer number has a higher priority, which means both customer and plant numbers are returned, then the allocation program takes over the customer number (and redefines the plant number). For every recipient, the source of supply can be returned as well (optional).
If errors occur in the function module (or SAP Notes have to be read), the numbers from the corresponding system messages (and the data belonging to them) in table EX_MESSG can be returned to the allocation program. This program can output the messages in log format.
Your system is configured as an SAP Retail System.
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional 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_ZF_VK_0611 | 0 | I020004210 | Allocation |
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_EMFIN | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20011018 |
| SAP Release Created in | 470 |
