Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-ISR-RSL (Application Component) Retail Stock Ledger⤷
RS_AA_WRMA (Package) Analytical Application RMA - Retail
IMG Activity
| ID | W_RMA_0024 | Define Access Condition Types |
| Transaction Code | S_BC6_84000007 | (empty) |
| Created on | 20010808 | |
| Customizing Attributes | W_RMA_0000 | RMA Attributes |
| Customizing Activity | W_RMA_0024 | Define Access Condition Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | W_RMA_0024 |
Use
In this work step, you can define the access condition types. With these access conditions, you can access the condition tables via the access sequences. You can use access condition types for defining the condition types. This way, you can prevent having to define an access sequence for each condition type.
The access condition type is also used for sending the RMA results to Financial Accounting. You assign an access condition type to a category for this reason.
You must specify whether an access condition type is relevant for the RMA reporting. In this case, the system filters out the exact access condition type for which the flag is set during the update to the InfoCube 0RMA_C01.
When using condition types in calculation schemas, negative values may occur, for example during calculation of the quotient of the cost price and the sales price. In this case, the system triggers a message.
Define the following for the access condition type:
- Whether the system should display a message
- Whether the message is an error or a warning
Assign the access condition types of category 11 (planned shrinkage) to a shrinkage access sequence and an update condition type for the resolution of the planned shrinkage. In addition, define these update condition types as access condition types of category 12 (resolution of planned shrinkage), using the same name.
Requirements
Standard settings
We deliver a range of access condition types that enable you to perform a general RMA calculation.
Activities
Example
You have defined the condition types P_PURC (purchases in one period) and (purchases according to year to date). However, the data is stored under PURC in the condition tables, as data is saved here periodically. For this reason, the access condition type used for storing the data on the database is stored for the condition types.
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
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 |
| V_WRMA_T685Z | V - View | SM30 |
History
| Last changed by/on | SAP | 20071205 |
| SAP Release Created in | 30A |
