Ansicht
Dokumentation
/AFS/SIMGARUN_RELSPC - Define Release Rules for Special SD Functions
Fill RESBD Structure from EBP Component Structure RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
In this IMG section you can define release rules which you will use to control the allocation in documents with VAS materials or BOM materials.
You can decide whether VAS materials will be considered by the allocation run and if so, how.
Hint
If you only use VAS types but do not use your own VAS materials to add value-added services, you must not make any special settings for handling the value-added services during the allocation. This is also true even if you use VAS materials but they are not relevant for requirements.
You have the following two options for defining a release rule for VAS materials:
- You can set the allocation run so that VAS materials are treated exactly like normal AFS materials. Each of the VAS items will then be individually assigned according to their availability.
- You can also determine that the value-added services are only assigned according to the available main material. In this case, those materials will also only be released for delivery if there is sufficient availability of the value-added services.
Example
You carry a material with complicated packing. It is therefore necessary that your customers only receive the goods completely packed. At the same time you want to make sure that no individual packings are shipped. Your customer needs 100 pieces of an SKU of this material. These 100 pieces are available, but there is only enough packing material available for 95 pieces. If you execute a release check with reference to the main item for the packing material, the 100 pieces of the SKU will not be released for delivery. Depending on the setting of your ARun type, you can either wait to deliver until there is enough packing material or you can first deliver 95 pieces of the SKU and the rest later.
Here you can make the setting for how sales BOMs will be considered by the allocation run. You decide whether the system should reduce the total quantity of the BOM accordingly if there is a stock shortage of one single component. This ensures, for example, that the components will only be allocated in the quantity ratio specified by the BOM. If you enter a minimum quota, the system will check whether all the components are at least available in that quantity. If not, it then cancels the allocation of the total item.
Example
Sales BOM A consists of components 1 and 2. 10 pieces of component 1 and 15 pieces of component 2 are required. A customer needs 20 pieces of this BOM. That means that you need 200 pieces of component material 1 (10x20) and 300 pieces of component material 2 (15x20). However, there are only 180 pieces of component 1 in warehouse stock. With the appropriate setting for the release check, the BOM will only be released during the allocation in the quantity in which it can be allocated when the specified quantity ratios are also considered. In this case, only 18 pieces of the BOM can be delivered to the customer at first.
Hint
You can use BOMs in the sales order as an assortment or as a prepack. You have to define a special control in the ARun release check for prepacks. Prepacks are only processed as units, which always takes place at main item level (never at component level). That way only the stock situation of the header material is checked in prepacks even during the allocation run.
- Define your release rules for value-added services or BOMs by assigning an alphanumeric key with a maximum of four characters as well as an informative text.
- Make the appropriate settings in your rule (minimum quotas per release level, final actions).
- Assign your relase rule to a global release rule.
rdisp/max_wprun_time - Maximum work process run time SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4218 Date: 20240425 Time: 111831 sap01-206 ( 140 ms )
