ale-dp/sap-fiori-apps huggingface dataset:
Maintain User Group - Price Planning Layout
Application component: Price Planning Workbench
App type: SAP GUI
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Enhance Price Planning Worklist
Application component: Price Planning Workbench
App type: SAP GUI
Description:   You use this report to enrich the markdown profiles that you have transferred from SAP BI to SAP ECC with data that the system requires to perform price planning.  The enriched markdown proposals remain in the worklist until it is reorganized if they are not selected in a price plan. 
Key features:   The report performs the following functions during the enhancement process:  Checks plausibility  Determines related markdown proposals if the level of the markdown proposal does not correspond to the specified pricing reference article assignments  Flags related markdown proposals  Determines different price activation levels  Determines stock information  Determines the assignment of the article to the article hierarchy or merchandise category hierarchy  Determines the budget belonging to the article  Determines the price planner group using the budget Note  You can use a Business Add-In (BAdI) to adapt the report to your requirements.For more information, see the Implementation Guide (IMG) for  Logistics - General under Price Planning  Enhancements Using Business Add-Ins  Additional Processing in the Worklist for Markdowns.  You use a BadI to determine related markdown proposals. In the default implementation, the system determines the markdown proposals that are related to a markdown proposal for a generic article variant by calling all other variants of the generic article that do not have their own markdown proposal.For more information, see the Implementation Guide (IMG) for  Logistics - General under Price Planning  Enhancements Using Business Add-Ins  Determine Related Markdown Proposals in the Worklist.   Selection  You must set at least one indicator in the Status of Markdown Proposal group box.   You can enter additional selection criteria to limit the selection of markdown proposals.  For markdown proposals that are to be enriched, you must enter a default start date for the validity period. When it transfers the markdown proposals to a price plan, the system copies this date to the header data.   Output  Once you have run the report, the system creates an application log for object WRF_PPW, subobject WORKLIST for any errors or warnings that have occurred. If you run the report online, the system also creates statistics relating to the execution of the program.  
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Delete Markdown Proposals - Price Planning
Application component: Price Planning Workbench
App type: SAP GUI
Description:   You can use this function to delete markdown proposals from the worklist in SAP ECC. Deleting markdown profiles reguarly can help improve performance when processing markdown proposals and prevents old data from being processed. 
Key features:  Selection  You must set at least one indicator in the Status of Markdown Proposals group box.   You can enter additional selection criteria to restrict the selection of markdown proposals.  Under Retention Period , you enter either the age in days or a key date.    Output  After you have run the report, the system displays a list of the deleted markdown proposals.  
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Define Workbench Layout - Price Planning
Application component: Price Planning Workbench
App type: SAP GUI
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Display Application Log - Price Planning
Application component: Price Planning Workbench
App type: SAP GUI
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Create Price Level Group
Application component: Price Groups
App type: SAP GUI
Description:   You create price level groups, the price patterns for them, and the corresponding price levels. After the data has been saved, you can assign it to an article group. 
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Maintain Price Level Group
Application component: Price Groups
App type: SAP GUI
Description:   You change the individual components of a price level group. You can display the article groups in which the price level group is used. 
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Display Price Level Group
Application component: Price Groups
App type: SAP GUI
Description:   You change the individual components of a price level group. You can display the article groups in which the price level group is used. 
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Display Changes - Price Level Groups
Application component: Price Groups
App type: SAP GUI
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Assign Merchandise Categories - Price Level Groups
Application component: Price Groups
App type: SAP GUI
Description:   You can assign price level groups to article groups using the appropriate maintenance transactions for the article groups. When there is a large number of price level groups to be assigned this can be very time consuming.  This function allows you to drag and drop assignments between merchandise categories and price level groups. 
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Reorganize Price Level Groups
Application component: Price Groups
App type: SAP GUI
Description:   Price level groups are transferred to SAP BW for reporting purposes and are therefore not deleted from the system in the normal way. To prevent data inconsistencies between the two systems, a special logic is used to delete data from the system with a time delay. Price level groups are retained in SAP BW even if they have been deleted from SAP Retail.  This function allows you to reorganize price level groups. You can schedule this program to run at periodic intervals so that the price level groups are organized regularly.  Reorganizing price level groups means checking to see that they are still valid. If a price pattern has expired, a deletion indicator is set for it. After a waiting period of at least a day, this price pattern is deleted along with all the related price levels. If all price patterns have been deleted from a price level group, the price level group itself is deleted from the database.  If you set deletion indicators manually, the system waits at least a day before it really deletes all the data.  If a price level group is to be deleted, it must no longer belong to an article group. The reorganization program therefore checks this before deleting price level groups. 
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Maintain References - F&R Integration
Application component: Forecasting and Replenishment backend integration
App type: SAP GUI
Description: This function enables you to prepare requirements planning for new articles for which there is no historical sales data yet. You can use it in SAP S/4HANA to assign one or more reference articles manually or automatically to an article-site combination (reference assignment). The system groups these assignments in a reference module. Once this data has been transferred to SAP F&R, you in your role as replenishment planner can plan a new article there with the historical data of one or several reference article(s). The reference modules created in SAP S/4HANA and their assignments to articles are only used operatively in SAP F&R. 
Key features: You can create a new reference module manually or automatically and assign it to a new article. You can create one assignment per article and site. The reference module can consist of any number of reference articles, which you can weight individually. You can change existing reference modules and assign them manually or automatically. When you assign references automatically, the system looks for suitable reference articles using several criteria, including the following: Merchandise category Article hierarchy Article attributes You can assign weighted articles to a reference determination schema stored in the article master. Before assigning, the system carries out a listing check and evaluates the listing periods . During automatic processing, you also have to take into consideration that: Changes to the merchandise category and the article hierarchy do not automatically lead to new reference assignments. You can use general settings in Customizing to stop the system overwriting existing references. If the Customizing setting for the structured article is changed after you have created the reference assignment, the reference assignment is not automatically adjusted. During manual processing, you can use the following functions: You can transfer reference module assignments for new articles to other plants. For more information, see Outbound Interface for Reference Modules . Where-used list for a reference module The where-used list contains all combinations of article and site to which the reference module is assigned. You assign the single reference or the reference module in the master data for the article. If you change a reference module or the assignment of a reference module to a new article, SAP S/4HANA creates change pointers which enable you to transfer the assignment or the reference module to SAP F&R anew. 
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Generate Reference Assignment - F&R Integration
Application component: Forecasting and Replenishment backend integration
App type: SAP GUI
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Delete Listings - Distribution Center
Application component: Listing
App type: SAP GUI
Description: This function checks the listing conditions of distribution center assortments and deletes the listing conditions if the articles belonging to it are no longer listed in any store. By doing this you prevent further replenishment of these articles in the distribution center. This is particularly important if you are using SAP Forecasting and Replenishment (SAP F&R). 
Business roles: Assortment Specialist - Retail
Apply Price Changes - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Create Worklist of Price Changes - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Process Worklist of Price Changes - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Analyze Price Changes - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Request Messages - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Create Supplier Settlement List
Application component: Settlement Management
App type: SAP GUI
Description: You can enter several incoming invoices for a single supplier in a supplier settlement list. The supplier settlement list can contain different customers. In contrast to list entry for inbound invoices, you can enter invoices with different settlement document types in a supplier settlement list. For more information see List Entry of a Settlement Document and Entering a Settlement Document and Creating Follow-On Documents.
Change Supplier Settlement List
Application component: Settlement Management
App type: SAP GUI
Key features: The advantage of using supplier settlement lists is the actual reduction of accounting documents stored in your system. Although an accounting document is generated from each individual document when settlement documents are created individually or in lists, the settlement documents contained in a supplier settlement list are not posted as single documents. These documents are posted using the supplier settlement list. Regardless of how many individual documents the list contains, only one accounting document is created. The individual documents have the posting status Post using Settlement Lists because the supplier and customer accounts are processed in the list and not as the individual settlement documents in the list. A supplier settlement list is saved in the system with its own document number. The settlement documents contained in the list are also saved as individual documents. You can use a supplier settlement list to credit the relevant supplier account. As the list can contain various customers, you must create a customer settlement list to debit the individual customer accounts. In the customer settlement list, the individual documents are grouped by customer. As an alternative to using the customer settlement list, you can generate a customer settlement for each customer. For more information, see Customer Settlement List and Customer Settlement.
Display Supplier Settlement List
Application component: Settlement Management
App type: SAP GUI
Key features: The advantage of using supplier settlement lists is the actual reduction of accounting documents stored in your system. Although an accounting document is generated from each individual document when settlement documents are created individually or in lists, the settlement documents contained in a supplier settlement list are not posted as single documents. These documents are posted using the supplier settlement list. Regardless of how many individual documents the list contains, only one accounting document is created. The individual documents have the posting status Post using Settlement Lists because the supplier and customer accounts are processed in the list and not as the individual settlement documents in the list. A supplier settlement list is saved in the system with its own document number. The settlement documents contained in the list are also saved as individual documents. You can use a supplier settlement list to credit the relevant supplier account. As the list can contain various customers, you must create a customer settlement list to debit the individual customer accounts. In the customer settlement list, the individual documents are grouped by customer. As an alternative to using the customer settlement list, you can generate a customer settlement for each customer. For more information, see Customer Settlement List and Customer Settlement.
Monitor Replenishment
Application component: Rapid Replenishment
App type: SAP GUI
Description: You can use the replenishment monitor to analyze the results of replenishment planning. It displays information such as which items were successfully processed, and in which items errors occurred. For the items with errors, you can analyze the cause. You identify the replenishment run that you want to analyze via the number that was issued internally by the system. 
Key features: In the replenishment monitor, the results are divided into the following categories: Successfully processed Work item generated Errors occurred Each category contains information about how the items (a combination of recipient and article) were processed. You can view the potential results of the replenishment run when follow-on documents are generated in test mode when planning is executed online. Errors that occurred during the generation of follow-on documents are also displayed. You cannot go to the follow-on documents themselves, since the documents have not yet been stored on the database at this time. From test mode, you can trigger the posting of documents in the database after you have checked the potential results. Note A number is assigned to every potential follow-on document even when follow-on documents are generated in test mode. The number is taken from the relevant number range. If you exit test mode without posting documents in the database, their current number levels are increased nonetheless. The document numbers assigned in test mode are therefore “used”, and they can no longer be assigned to other documents. 
Business roles: Demand Planner (Retail)| Replenishment Specialist - Store (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.

Replenishment Specialist - Store (Retail) : 
Is responsible for the automated replenishment of retail stores with merchandise. Reviews calculated quantities and delivery schedules. Monitors and analyzes service levels, stock development and out of stock situations.
Execute Rapid Replenishment
Application component: Rapid Replenishment
App type: SAP GUI
Business roles: Demand Planner (Retail)| Replenishment Specialist - Store (Retail)
Replenishment Specialist - Store (Retail) : 
Is responsible for the automated replenishment of retail stores with merchandise. Reviews calculated quantities and delivery schedules. Monitors and analyzes service levels, stock development and out of stock situations.

Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Maintain Price Band Categories
Application component: Merchandise Categories
App type: SAP GUI
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Maintain Price Point Groups
Application component: Merchandise Categories
App type: SAP GUI
Business roles: Category Manager (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Monitoring Tool for Web Services - Portugal
Application component: Portugal
App type: SAP GUI
Business roles: Billing Clerk for Portugal
Billing Clerk for Portugal: (is an add-on role to the Billing Clerk)
Processes invoices in time, monitors and manages the invoice process, works on a prioritized worklist (e.g. sorted by invoice date and value of invoice requests), creates, releases, and sends invoice documents.
Set Stock Situation
Application component: Goods Receipt
App type: SAP GUI
Key features:   Before the report processes sales made at POS terminals, it checks whether the stock situation is ambiguous or unique. Note  The report only takes into account the unrestricted-use stock for the articles in a site.  If the stock situation is unique , the system can post the goods without stock determination. If, for example, only consignment stock for a vendor or only your own stock is present, the situation is unique.   If the stock situation is ambiguous , the system performs stock determination before posting the goods. If, for example, consignment stock exists for several vendors, the stock situation is ambiguous .    To combine the components of structured articlesin the consignment stock that the system expanded during the goods receipt, the stock situation must be unique.  Note  You can use a Business Add-In (BAdI) to adapt the report functions to your requirements.For more information, see the Implementation Guide (IMG) for  Logistics - General under Retail Consignment Processing  Enhancements Using Business Add-Ins  BAdI: Extensions for Consignment Processing.   
Business roles: Allocator (Retail)| Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.

Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Analyze Application Log - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Display Application Log - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Maintain Procedures for Customers - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Display Procedures for Customers - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Archive Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Maintain Procedures for Suppliers - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Display Procedures for Suppliers - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Assign Additionals to Articles
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
List Documents - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Generate Purchase Orders - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Analyze Changes - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Execute Trading Processes
Application component: Trading Execution Workbench
App type: SAP GUI
Business roles: Trader
Trader : 
Buys and sells physical products with a special focus on profitability and end to end service.
Request Messages for Article - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Request Messages for Promotion - Additionals
Application component: Additionals Management
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Process Claim - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:  The layout refers to the display of the warranty claim in transaction WTY (Warranty Claim Processing).
Maintain Authorization - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You use this process if you want to authorize a claimant to submit a warranty claim for an object for which, according to the warranty conditions, there is no longer a warranty. In other words, you want to make use of goodwill . The system can then check this authorization and process the claim automatically .
Create Credit Memo List - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You can use this process if you want to simplify the posting of credit memos to your customers/claimants .   In the course of warranty claim processing, one or more credit memos are created for the claimant per warranty claim and then posted to accounting. It does not make sense to send each individual credit memo to the customer/claimant separately; it would seem more sensible to collect the credit memos together and send them all at once at a later date in the form of a credit memo list .  Caution  This function is only offered for postings to customer accounts (credit memos to the customer/claimant) and not for postings to vendor accounts (debit memos to the vendor/reimburser).
Claim Worklist - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:  This following describes the standard process for warranty claim processing. in postcrediting cases, i.e.: cases in which the claimant is not provided with a credit memo until an answer has been received from the reimburser. in precrediting cases, i.e.: cases in which the claimant is provided with a credit memo immediately and the claim is then sent to the reimburser later.
Process Query - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   As the person responsible or as the manager for warranty claim processing in the SAP Discrete Industries System you can use online reporting to create ad hoc reports for warranty claim processing . Examples for possible reports are:   all claims for which the sum that the claimant makes lies within specific amount restrictions  all claims with parts that have to be returned  all claims for a specific vehicle model  all claims of a specific claimant  all claims in which a specific replacement part is contained  
Key features:   You can use online reporting both to define basic reports, i.e.: define and save selection criteria and report layouts, and to create the reports yourself . You cannot, however, save the results in the system.   You can evaluate data that is created in warranty processing itself and external data that warranty processing uses, for example data on the customer, vendor, material, warranty object and so on. However, not all the fields of these object masters are available, only the most important ones. All this data can be used as selection criteria and as output fields in the report.   The SAP standard system delivery contains user group WTY_OR for warranty claim processing. The InfoSet WTY and the logical database WTY is assigned to this user group. All the available warranty claim processing data is contained in the InfoSet WTY.
Maintain Recalls - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You use this process if you want to enter and process warranty claims with reference to a recall.  In a recall , products that have already been sold are recalled publicly to production so that a serious defects or technical errors in the object can be rectified. The costs of rectifying the defect are carried by the reimburser or claim processor , even if the warranty conditions are no longer fulfilled. We are therefore dealing here with a special form of warranty claim processing.   The same applies to a technical campaign, but without the products being recalls publicly. For all products that have to be maintained or repaired anyway, the technical error is eliminated at the same time without the end customer necessarily knowing. Note  There is no difference between processing with recalls and processing with technical campaigns in warranty claim processing. This documentation therefore just refers to recalls .
Process Parts Return - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You use this process if you do not want to process warranty claims until the claimant has returned specific faulty parts to you or to the reimburser to be checked. In this way you can, for example, discover why a particular part is always defective and thus ultimately improve your quality assurance processes.
Display Claims from Archive - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:  You can archive completed and paid warranty claims (that you only require for reporting and displaying history) in the background and thus reduce the load on the database. In this way you can improve performance when searching for and processing current claims. SAP makes no particular recommendations as to when warranty claims should be archived since warranty claim processing can be used very flexibly and therefore the business requirements can be very different in this respect. 
Key features:  Transaction WTY_SARA is used to write archiving data. This transaction corresponds to the standard transaction SARA. The archiving object is WTY_CLAIM. There is only a limited technical display for reading the archiving data in this transaction. The application-specific transaction WTY_ARCHIV offers a better display of the archived warranty claims.The system checks the following authorization objects: C_WTY_OBJ and C_WTY_STAT.The following data is archived:Header/version/item data Long texts Recall objects Recall history Pricing data Messages Change documents Relationships to measurement documents Customer fields are automatically archived as well. The documents associated with the warranty claim (credit memo/debit memo, measurement documents, sales orders etc.) and warranty object master data (installation, equipment etc.) are not archived. Each archiving run is logged by the system.You can also execute archiving in test mode . Caution Archived warranty claims cannot be reloaded/restored.
Archive Claims - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:  You can archive completed and paid warranty claims (that you only require for reporting and displaying history) in the background and thus reduce the load on the database. In this way you can improve performance when searching for and processing current claims. SAP makes no particular recommendations as to when warranty claims should be archived since warranty claim processing can be used very flexibly and therefore the business requirements can be very different in this respect. 
Key features:  Transaction WTY_SARA is used to write archiving data. This transaction corresponds to the standard transaction SARA. The archiving object is WTY_CLAIM. There is only a limited technical display for reading the archiving data in this transaction. The application-specific transaction WTY_ARCHIV offers a better display of the archived warranty claims.The system checks the following authorization objects: C_WTY_OBJ and C_WTY_STAT.The following data is archived:Header/version/item data Long texts Recall objects Recall history Pricing data Messages Change documents Relationships to measurement documents Customer fields are automatically archived as well. The documents associated with the warranty claim (credit memo/debit memo, measurement documents, sales orders etc.) and warranty object master data (installation, equipment etc.) are not archived. Each archiving run is logged by the system.You can also execute archiving in test mode . Caution Archived warranty claims cannot be reloaded/restored.
Assign User Profile - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:  The layout refers to the display of the warranty claim in transaction WTY (Warranty Claim Processing).
Create Documents - Physical Inventory
Application component: Physical Inventory
App type: SAP GUI
Business roles: Allocator (Retail)
Inventory Manager (Retail) : 
Manages inventory with respect to quantity and value.

Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Create Planned Markup
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Maintain Planned Markup
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Display Planned Markup
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Create Planned Markup - Price List
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Maintain Planned Markup - Price List
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Display Planned Markup - Price List
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Recompile Index Pricing Documents
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Simulate Store Order Processing - POS Inbound
Application component: POS Interface - Inbound
App type: SAP GUI
Business roles: Administrator (Retail)
Administrator (Retail) : 
Performs retail specific administration tasks on application level, such as POS interface monitoring.
Send Documents - Physical Inventory
Application component: Physical Inventory
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Simulate Physical Invent. Processing - POS Inbound
Application component: POS Interface - Inbound
App type: SAP GUI
Business roles: Administrator (Retail)
Administrator (Retail) : 
Performs retail specific administration tasks on application level, such as POS interface monitoring.
Execute Replenishment - Customer Replenishm.
Application component: Forecasting Procedures
App type: SAP GUI
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Send Sales and Stock - Supplier Replenishm.
Application component: Forecasting Procedures
App type: SAP GUI
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Display Transferred Sales and Stock - Supplier Replenishm.
Application component: Forecasting Procedures
App type: SAP GUI
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Display Sales and Stock - Customer Replenishm.
Application component: Forecasting Procedures
App type: SAP GUI
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Display Replenishment Parameter - Customer Replenishm.
Application component: Forecasting Procedures
App type: SAP GUI
Business roles: Demand Planner (Retail)
Demand Planner (Retail) : 
Is responsible for forecasting the demand for all different customer sales channels as input to supply and inventory planning.
Generate Sales Price Worklist
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Release Sales Price Worklist - by Article
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Release Sales Price Worklist - by Organization
Application component: Retail-Pricing
App type: SAP GUI
Business roles: Category Manager (Retail)| Pricing Specialist (Retail)
Category Manager (Retail) : 
Manages the assortment and sales figures of a given product category at a retailer.
Maintain Purchase Orders - Order Optimizing
Application component: Planning Workbench
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Adjust Purchase Orders - Order Optimizing
Application component: Planning Workbench
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Create Output - Settlement Management
Application component: Settlement Management
App type: SAP GUI
Description: You create condition records for a message type for suppliers and customers. For each supplier and customer, you can also maintain further parameters for message output, if required. These parameters then override the data that is maintain as default values in Customizing for the message type. The following procedure describes to create condition records for the message types defined in Customizing.
Change Output - Settlement Management
Application component: Settlement Management
App type: SAP GUI
Description: In the Settlement Management component, you use this process to create messages for settlement management documents, which supports communication with your business partners.
Display Output - Settlement Management
Application component: Settlement Management
App type: SAP GUI
Description: In the Settlement Management component, you use this process to create messages for settlement management documents, which supports communication with your business partners.
Create Message Determination Condition Records - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You can automate the output or subsequent processing of partner-dependent messages by using message determination. The application calls message determination via defined interfaces.   You can use these interfaces to describe different data constellations and the desired processing methods. If one of these data constellations occurs in the application, appropriate processing is started either synchronously or asynchronously. You can define the processing in numerous ways, for example, as workflow, printout or as IDoc for EDI.   You can use message determination in Warranty Claim Processing to trigger the printing of credit memos , for example, and/or to forward warranty claim versions that have been received and processed via IDoc/EDI to the reimburser or claimant .  
Key features:   Message determination procedure WTY001 with the following message types is delivered with the standard system:  W001 Printout/fax of credit memos  WTOC Shipping of warranty claim versions using IDoc/EDI. This message type has access sequence 0005. In this access sequence, the first access refers to condition records for the key Partner Type , the second access to condition records for the keys Release for Sending and Partner Type .  Note  This message type is restricted to partner types LI (vendor) and KU (customer).
Change Message Determination Condition Records - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You can automate the output or subsequent processing of partner-dependent messages by using message determination. The application calls message determination via defined interfaces.   You can use these interfaces to describe different data constellations and the desired processing methods. If one of these data constellations occurs in the application, appropriate processing is started either synchronously or asynchronously. You can define the processing in numerous ways, for example, as workflow, printout or as IDoc for EDI.   You can use message determination in Warranty Claim Processing to trigger the printing of credit memos , for example, and/or to forward warranty claim versions that have been received and processed via IDoc/EDI to the reimburser or claimant .  
Key features:   Message determination procedure WTY001 with the following message types is delivered with the standard system:  W001 Printout/fax of credit memos  WTOC Shipping of warranty claim versions using IDoc/EDI. This message type has access sequence 0005. In this access sequence, the first access refers to condition records for the key Partner Type , the second access to condition records for the keys Release for Sending and Partner Type .  Note  This message type is restricted to partner types LI (vendor) and KU (customer).
Display Message Determination Condition Records - Warranty Claim Processing
Application component: Warranty Claim Processing
App type: SAP GUI
Description:   You can automate the output or subsequent processing of partner-dependent messages by using message determination. The application calls message determination via defined interfaces.   You can use these interfaces to describe different data constellations and the desired processing methods. If one of these data constellations occurs in the application, appropriate processing is started either synchronously or asynchronously. You can define the processing in numerous ways, for example, as workflow, printout or as IDoc for EDI.   You can use message determination in Warranty Claim Processing to trigger the printing of credit memos , for example, and/or to forward warranty claim versions that have been received and processed via IDoc/EDI to the reimburser or claimant .  
Key features:   Message determination procedure WTY001 with the following message types is delivered with the standard system:  W001 Printout/fax of credit memos  WTOC Shipping of warranty claim versions using IDoc/EDI. This message type has access sequence 0005. In this access sequence, the first access refers to condition records for the key Partner Type , the second access to condition records for the keys Release for Sending and Partner Type .  Note  This message type is restricted to partner types LI (vendor) and KU (customer).
Create Settlement Document
Application component: Settlement Management
App type: SAP GUI
Description:  With this app, you can quickly access all relevant data of a settlement document in one place. Get a comprehensive overview of all key facts of the settlement document such as involved business partners, administrative and contractual data, as well as document items. With the full document flow, you can immediately see the current status of the settlement document and all related documents. The app helps you to easily analyze settlement document data and determine follow-up actions. 
Key features:    Check the key fields of the settlement document easily such as status, accounting data, and gross settlement amount    Display account assignment information   Navigate to related apps, for example, the Monitor Settlement Documents app   Display additional information about the settlement document such as basic settlement data and currency and posting information   Display administrative and contractual data   Display relevant journal entry and contract accounting data   Display a list of business partners and access additional partner data by selecting a business partner   Display pricing information   Select individual settlement document items to view item information such as the supplier and customer item net amount   Analyze the full document flow in a detailed way   Display a list of output items and open the corresponding PDF files
Collect Settlement Documents
Application component: Settlement Management
App type: SAP GUI
Business roles: Accounts Payable Accountant - Procurement| Billing Clerk| Settlement Clerk - Royalties| Settlement Clerk
Settlement Clerk : 
Is responsible for third-party financial settlement processes, settling contractual rebate agreements and for keeping track of settlement management documents and payments.

Accounts Payable Accountant : 
Carries out the most important functions in accounts payable accounting with a special focus on creation and execution.

Accounts Payable Accountant - Procurement : 
Carries out the most important functions in accounts payable accounting with a special focus on supplier invoice processing.

Settlement Clerk - Royalties : 
Is responsible for third-party financial settlement processes, settling contractual royalty agreements and for keeping track of settlement documents and payments.

Billing Clerk : 
Processes invoices in time, monitors and manages the invoice process, works on a prioritized worklist (e.g. sorted by invoice date and value of invoice requests), creates, releases, and sends invoice documents.
Display Parameters of Articles - Merchandise Distrib.
Application component: Merchandise Distribution
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.
Display Parameters of Sites - Merchandise Distrib.
Application component: Merchandise Distribution
App type: SAP GUI
Business roles: Allocator (Retail)
Allocator (Retail) : 
Is responsible for the distribution of products from distribution centers to stores throughout the lifecycle of these products.