Ansicht
Dokumentation

EM_DEF_PRC_CTRL - Define Process Control

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

You can this IMG activity to define settings to control the process and how the data are updated to DMR. Further the mapping between materials and categories is determined.

In the last step the layout and content of some of the fields displayed is determined.

• Process Control

Here the basic settings are determined how the DMR is updated. The settings are either done just by sales document type or by the combination of sales document type and sales organization

1. ,,Enter sales document type of the resource related DMR being processed
2. ,,If rules differentiate by sales organization, then enter sales organization else leave it blank
3. ,,Enter the rejection reason used to update rejections to the DMR
4. ,,Mark if split functionality is allowed
5. ,,Enter the condition type being used for updating the accrual value
6. ,,Enter the condition type being used to enter the value changes triggered in value screen
7. ,,Enter the text ID being updated

• Categories for Materials

Here the mapping between DMR lines to categories are maintained. All materials used on a DMR of the respective document type and sales organization needs to be mapped to a category. Otherwise an error occurs when processing the DMR

1. ,,Mark the row with relevant sales document type /sales organization combination
2. ,,Select categories for materials
3. ,,List materials used on DMR and map each material to a category ID

Note

All materials need to be mapped, not only the one originally being used on DMR, but also these being added during processing.

The billing request editor poses certain restrictions on the pricing functionality used on DMR, following are the restrictions:

• No non linear prices, a change in quantity must be reflected in a linear change of price. (For example a pricing where up to 5 h cost 100 per h and everything above would only cost 80 per hour could not be supported)

• No conditions which interfere with the conditions are used for accrual and value update (Example if the value update would set a DMR line to 100 and we would have additional conditions afterwards, which overrule this the billing request editor would not work)

• Condition types used for update need to be set up so that 0 is considered a valid entry (see oss note 40086, mark condition type as group condition)

• Material for categories

Here the materials are defined, which are used while adding additional lines to the DMR. Only one material per category shoul d be used. Mark the row with relevant sales document type /sales organization combination

1. ,,Select materials for categories
2. ,,Maintain for each category being used, which is not assigned to usage 00030 one material

Note

Materials need to be generated in respective sales organization; otherwise errors occur when processing the DMR.

• Screen Values

Per sales document type and sales organization (optional) values are defined, from which fields values are sourced and are displayed in the billing request editor. The column headings where these values are shown can be defined here as well

1. ,,Define sales document type of DMR being processed
2. ,,Define the relevant sales organization if different by sales organization, else leave it blank
3. ,,Select from the drop-down list relevant field from VBAP, which should be used in first column of WIP screen.

Note:This is also the value with which system operates on WIP screen and accrual screen.

1. ,,Define the column title for the first column
2. ,,Define value for the second column (if not required leave blank)

Example: If you do your WIP selection based on revenue you could use the second column to display the valuation at cost.

1. ,,Define description for the second column
2. ,,Define description for the first column and second column in the value screen
3. ,,Save your entries

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5103 Date: 20240523 Time: 195215     sap01-206 ( 70 ms )