ale-dp/sap-fiori-apps huggingface dataset:
My Purchase Order Items - Due for Delivery
Application component: Basic Functions
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
My Sales Order Schedule Lines - Due for Delivery
Application component: Basic Functions
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist : 
Processes outbound deliveries.

Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.
My Purchase Order Schedule Lines - Due for Delivery
Application component: Basic Functions
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
My Documents - Due for Delivery
Application component: Basic Functions
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist : 
Processes outbound deliveries.

Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.
My Items - Due for Delivery
Application component: Basic Functions
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist : 
Processes outbound deliveries.

Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.
Handling Units due for Delivery
Application component: Handling Unit Management
App type: SAP GUI
Description:  You can create outbound deliveries for handling units that have already been created, in production or elsewhere. Example ScenarioThe Sales & Distribution planner monitors the documents that are due for delivery and creates outbound deliveries at the appropriate time. Handling units have already been created in production and assigned to the customer requirements. The planner calls up a list containing both the delivery-due documents and the handling units already created and assigned to them, and creates the deliveries accordingly. 
Key features:  You can call up a list of documents that are due for delivery, handling units that have already been created for these documents (with status "GR-posted") and open deliveries. In this list, you can select handling units and a delivery-due document and have the system create a delivery for them assign handling units to open deliveries change the assignment of a handling unit (that is, assign it to a different sales order or to a different delivery) assign non-assigned handling units to sales orders  
Shipping Specialist : 
Processes outbound deliveries.
My Schedule Lines - Due for Delivery
Application component: Basic Functions
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist : 
Processes outbound deliveries.

Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.
VL10 (technical)
Application component: Delivery Processing
App type: SAP GUI
Description:   Operations (sales orders or purchase orders, for instance) are analyzed and delivered (transferred) for delivery creation according to their planned delivery-creation dates. The analysis gives you an overview of the work required. You can still make manual changes to the planned outbound delivery situation by using the selected delivery list (also called the shipping due date index or shipping due list). This may be used for the following operations:  Manual selection of documents to be delivered from a larger delivery list  Manual assignment of actual quantities to be delivered to delivery planning  In the introductory phase of setting automated outbound delivery creation   Collective delivery of multiple documents in one step may be especially helpful in the following situations:  If outbound delivery creation occurs regularly in the background. You can create rules for worklist creation in a user role for this delivery and work on the worklist regularly.   If the length of time needed between creating the transaction and actual outbound delivery (picking, shipment completion) is longer than the time it takes for picking and scheduling.   If multiple orders are to be combined into one delivery for a certain ship-to party.   
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
Create Inbound Delivery
Application component: Basic Functions
App type: SAP GUI
Scope items: Sales Processing using Third-Party with Variant Configuration|Customs Management with SAP Global Trade Services|Basic Warehouse Inbound Processing from Supplier with Quality Management|Warehouse Inbound Processing from Supplier with Batch Management
Description:  With this app, you can create inbound deliveries for delivery management. 
Key features:    Select a purchase order and supplier as the preceding document for the inbound delivery.   Create an inbound delivery   
Business roles: Operations Clerk (ACM)| Receiving Specialist| Settlement Clerk (ACM)
Accounts Payable Accountant for Russian Federation: (is an add-on role to the Accounts Payable Accountant)
Carries out the most important functions in accounts payable accounting with a special focus on creation and execution (for Russia).

Receiving Specialist : 
Processes inbound deliveries.

Settlement Clerk (Agricultural Contract Management) : 
Compiles and computes payment due and recoveries to be made for ACM.

Operations Clerk (Agricultural Contract Management) : 
Perform clerical or administrative duties in a variety of business for ACM.
Change Inbound Delivery
Application component: Basic Functions
App type: SAP GUI
Scope items: Scheduling Agreements in Procurement|Customs Management with SAP Global Trade Services
Description:  With this app, you can change a single inbound delivery. You can also navigate to other apps and process the the delivery. 
Key features:    Select a single inbound delivery by entering the inbound delivery ID   Change data for the selected delivery    View the document flow for the selected delivery   View the header data for the selected delivery   Post a goods receipt for the selected delivery   Pack the selected delivery   
Business roles: Operations Clerk (ACM)| Receiving Specialist| Settlement Clerk (ACM)
Settlement Clerk (Agricultural Contract Management) : 
Compiles and computes payment due and recoveries to be made for ACM.

Operations Clerk (Agricultural Contract Management) : 
Perform clerical or administrative duties in a variety of business for ACM. 

Receiving Specialist : 
Processes inbound deliveries.
Inbound Deliveries for Purchase Orders
Application component: Basic Functions
App type: SAP GUI
Scope items: Direct Procurement with Inbound Delivery|Sales Processing using Third-Party with Shipping Notificationx
Description:  With this app, you can select purchase orders that meet the selection criteria that you enter and create inbound deliveries form them. You can also do a test run to check how many inbound deliveries the app creates. 
Key features:    Select purchase orders with a delivery date up to a given date   Create inbound deliveries from these purchase orders   Simulate the delivery creation   
Business roles: Operations Clerk (ACM)| Receiving Specialist| Settlement Clerk (ACM)
Receiving Specialist : 
Processes inbound deliveries.

Settlement Clerk (Agricultural Contract Management) : 
Compiles and computes payment due and recoveries to be made for ACM.

Operations Clerk (Agricultural Contract Management) : 
Perform clerical or administrative duties in a variety of business for ACM.
Extended Inbound Delivery Processing
Application component: Basic Functions
App type: SAP GUI
Business roles: Operations Clerk (ACM)| Receiving Specialist| Settlement Clerk (ACM)
Settlement Clerk (Agricultural Contract Management) : 
Compiles and computes payment due and recoveries to be made for ACM.

Operations Clerk (Agricultural Contract Management) : 
Perform clerical or administrative duties in a variety of business for ACM. 

Receiving Specialist : 
Processes inbound deliveries.
Print Inbound Delivery - Manually, Print Outbound Delivery - Manually
Application component: Basic Functions
App type: SAP GUI
Business roles: Operations Clerk (ACM)| Receiving Specialist| Settlement Clerk (ACM)| Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Receiving Specialist : 
Processes inbound deliveries.

Settlement Clerk (Agricultural Contract Management) : 
Compiles and computes payment due and recoveries to be made for ACM.

Operations Clerk (Agricultural Contract Management) : 
Perform clerical or administrative duties in a variety of business for ACM. 

Shipping Specialist : 
Processes outbound deliveries.
Archive Deliveries
Application component: Basic Functions
App type: SAP GUI
Description:  Before you use the archiving object, check Application Customizing.
Rough Workload Estimate - Picking/Goods Issue Analysis
Application component: Basic Functions
App type: SAP GUI
Description:   These standard analyses enable the person in charge of a distribution center or warehouse to calculate the rough workload for the next few days. The analyses can be used, for example, for planning how many staff workers are required, for creating wave picks, or for statistical evaluations.  Using these analyses it is possible to display an overview of the workload either per day or per warehouse. The workload data update is based on SAP documents: Purchase order and corresponding shipping notification  Stock transport order  Rough goods receipt (only in retail systems)  Sales order  Delivery Returns to vendor, customer returns and store returns (only in retail systems)  The system updates the quantity, weight, volume, and the number of document items or stock allocations from these documents. Alternatively, processing times can be determined by using Customizing tables.
Archive Data - For Rough Workload Estimate
Application component: Basic Functions
App type: SAP GUI
Description:   These standard analyses enable the person in charge of a distribution center or warehouse to calculate the rough workload for the next few days. The analyses can be used, for example, for planning how many staff workers are required, for creating wave picks, or for statistical evaluations.  Using these analyses it is possible to display an overview of the workload either per day or per warehouse. The workload data update is based on SAP documents: Purchase order and corresponding shipping notification  Stock transport order  Rough goods receipt (only in retail systems)  Sales order  Delivery Returns to vendor, customer returns and store returns (only in retail systems)  The system updates the quantity, weight, volume, and the number of document items or stock allocations from these documents. Alternatively, processing times can be determined by using Customizing tables.
Rough Workload Estimate - Goods Receipt/Putaway Analysis
Application component: Basic Functions
App type: SAP GUI
Description:   These standard analyses enable the person in charge of a distribution center or warehouse to calculate the rough workload for the next few days. The analyses can be used, for example, for planning how many staff workers are required, for creating wave picks, or for statistical evaluations.  Using these analyses it is possible to display an overview of the workload either per day or per warehouse. The workload data update is based on SAP documents: Purchase order and corresponding shipping notification  Stock transport order  Rough goods receipt (only in retail systems)  Sales order  Delivery Returns to vendor, customer returns and store returns (only in retail systems)  The system updates the quantity, weight, volume, and the number of document items or stock allocations from these documents. Alternatively, processing times can be determined by using Customizing tables.
Rough Workload Estimate - General Overview
Application component: Basic Functions
App type: SAP GUI
Description:   These standard analyses enable the person in charge of a distribution center or warehouse to calculate the rough workload for the next few days. The analyses can be used, for example, for planning how many staff workers are required, for creating wave picks, or for statistical evaluations.  Using these analyses it is possible to display an overview of the workload either per day or per warehouse. The workload data update is based on SAP documents: Purchase order and corresponding shipping notification  Stock transport order  Rough goods receipt (only in retail systems)  Sales order  Delivery Returns to vendor, customer returns and store returns (only in retail systems)  The system updates the quantity, weight, volume, and the number of document items or stock allocations from these documents. Alternatively, processing times can be determined by using Customizing tables.
Rough Workload Estimate - Returns to Supplier Analysis
Application component: Basic Functions
App type: SAP GUI
Description:   These standard analyses enable the person in charge of a distribution center or warehouse to calculate the rough workload for the next few days. The analyses can be used, for example, for planning how many staff workers are required, for creating wave picks, or for statistical evaluations.  Using these analyses it is possible to display an overview of the workload either per day or per warehouse. The workload data update is based on SAP documents: Purchase order and corresponding shipping notification  Stock transport order  Rough goods receipt (only in retail systems)  Sales order  Delivery Returns to vendor, customer returns and store returns (only in retail systems)  The system updates the quantity, weight, volume, and the number of document items or stock allocations from these documents. Alternatively, processing times can be determined by using Customizing tables.
Rough Workload Estimate - Customer/Store Return Analysis
Application component: Basic Functions
App type: SAP GUI
Description:   These standard analyses enable the person in charge of a distribution center or warehouse to calculate the rough workload for the next few days. The analyses can be used, for example, for planning how many staff workers are required, for creating wave picks, or for statistical evaluations.  Using these analyses it is possible to display an overview of the workload either per day or per warehouse. The workload data update is based on SAP documents: Purchase order and corresponding shipping notification  Stock transport order  Rough goods receipt (only in retail systems)  Sales order  Delivery Returns to vendor, customer returns and store returns (only in retail systems)  The system updates the quantity, weight, volume, and the number of document items or stock allocations from these documents. Alternatively, processing times can be determined by using Customizing tables.
Goods Movement - For Handling Units and Materials
Application component: Basic Functions
App type: SAP GUI
Warehouse Clerk : 
Executes daily warehouse operations, such as carrying out stock transfers, analyzing stock-out situations, reverse material documents, etc.

Inventory Manager : 
Manages inventory with respect to quantity and value.
Change Outbound Delivery - Proof of Delivery
Application component: Basic Functions
App type: SAP GUI
Scope items: Sales Order Processing for Non-Stock Material|Delivery Processing without Order Reference|Sell from Stock
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
Display Outbound Delivery - Proof of Delivery
Application component: Basic Functions
App type: SAP GUI
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
Subsequent Processing - Proof of Delivery
Application component: Basic Functions
App type: SAP GUI
Description:  With this app, you can create a worklist for proofs of delivery (PODs) that require manual changes after a recipient has confirmed receipt of the delivery. It is important for deliveries in which the delivery quantity varies because of the nature of the goods or for which the exact delivery quantity is unknown from the start. After the delivery has been confirmed, the system creates a worklist for manual subsequent processing for any necessary quantity and value corrections, for example, the cost of sales. 
Key features:    Create a worklist for PODs that need manual changes based on information such as variance reason, POD date, or POD verification date   Filter the worklist   Access the PODs in the work list to make manual corrections   Set the status of the PODs to complete when you've finished making manual changes   
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
Deliveries Worklist - Proof of Delivery
Application component: Basic Functions
App type: SAP GUI
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.

Shipping Specialist : 
Processes outbound deliveries.
Automatic Confirmation - Proof of Delivery
Application component: Basic Functions
App type: SAP GUI
Description:  With this app, you can confirm the proof of delivery (POD) information you received from the ship-to party for one or multiple outbound deliveries in a simple way. Once done, the system displays a log with all processed outbound deliveries and success or error messages. In the log, you can navigate to a detailed view for each outbound delivery and verify that the POD status on outbound delivery header level has been changed to Confirmed for all successfully processed outbound deliveries. After the proof of delivery has been confirmed, the system creates a worklist for manual subsequent processing for any necessary quantity and value corrections, for example, the cost of sales. 
Key features:    Define selection criteria for outbound deliveries to be processed    Perform automatic confirmation of the proof of delivery for all selected outbound deliveries    Display a log with results for each selected outbound delivery    Navigate to any outbound delivery in the log to see further details (for example, the resulting POD Status)    
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist : 
Processes outbound deliveries.

Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.
Split Outbound Delivery
Application component: Delivery Processing
App type: SAP GUI
Scope items: Sell from Stock|Accelerated Customer Returns|Delivery Processing without Order Reference|Sales Order Processing for Non-Stock Material
Business roles: Shipping Specialist| Shipping Specialist - Just-In-Time Supply
Shipping Specialist : 
Processes outbound deliveries.

Shipping Specialist - Just-In-Time Supply : 
Processes outbound deliveries for Just-In-Time calls.
Launch VMP
Application component: Visual Manufacturing Planner
App type: SAP GUI
Business roles: Production Engineer - Discrete Manufacturing (CAM)| Production Engineer - Discrete Manufacturing (EME)
Production Engineer - Discrete Manufacturing (Complex Assembly) : 
Defines certifications required to work in a work center or process a certain material making sure only certified production operators perform critical production operations.

Production Engineer - Discrete Manufacturing (Manufacturing Engineering) : 
Translates engineering BOMs into manufacturing BOMs and creates detailed shop floor routings.
Cockpit for VMP
Application component: Visual Manufacturing Planner
App type: SAP GUI
Business roles: Production Engineer - Discrete Manufacturing (CAM)| Production Engineer - Discrete Manufacturing (EME)
Production Engineer - Discrete Manufacturing (Complex Assembly) : 
Defines certifications required to work in a work center or process a certain material making sure only certified production operators perform critical production operations.

Production Engineer - Discrete Manufacturing (Manufacturing Engineering) : 
Translates engineering BOMs into manufacturing BOMs and creates detailed shop floor routings.
Dunning Proposal Insurance
Application component: Collections and Disbursements
App type: SAP GUI
Description:  The dunning proposal run groups together the items due for dunning for a business partner and creates a dunning proposal from them. 
Key features: By specifying the corresponding selection criteria in the dunning proposal run, you control which items are dunned. The dunning proposal run reads the overdue items for a business partner and uses the following criteria to group the items in a dunning proposal into dunning groups (items to be dunned collectively): Dunning variant or dunning procedures defined for the master dataDays in arrearsDunning frequencyDunning levels already assigned If you want to define information about the collecting broker for an item due for dunning directly in one of the following two fields, the dunning block is checked in the broker contract specified in the document. Alternative Collecting Broker [ALTBROK]Broker Contract for Alternative Collecting Broker [ALTBRCO] If, for an item due for dunning, you define that this item is to be collected directly (Checkbox: Direct Collection [DIRCOLL]) regardless of any existing assignment to a broker, any existing dunning block for assigned insurance objects in the broker contract is ignored. In user exit V313, you can continue to process items due for dunning that cannot be dunned because of a dunning block for assigned insurance objects in the broker contract. You can delete a dunning proposal as long as the dunning proposal run has not started.
Dunning Activities
Application component: Collections and Disbursements
App type: SAP GUI
Description:  Once you have executed the dunning proposal run successfully, start the second subprocess of the dunning run – the dunning activity run.
Key features:  The dunning activity run determines and runs the dunning activities defined in the dunning procedures and dunning levels. A dunning activity run relates only to those overdue items determined in a dunning proposal run. If the dunning activity run carried out a dunning activity successfully, it sets the print date in the dunning proposal. The print date is the same as the run date. If errors occurred during the execution of the dunning activities run, the system only sets the print date in some of the dunning headers. If the cause of the error is in the dunning proposal, you have to reverse the dunning notices concerned. If the cause of the error is in the dunning activity run, you have to correct the error and then start the dunning activity run again for this dunning proposal run. In this second run, the dunning activity run only processes the dunning notices that have not been executed yet, that is, dunning notices that have not received a print date (run date). If a long time has elapsed since the error occurred, we recommend that you reverse the dunning notices that have not been executed manually or using the transaction Mass Reversal of Dunning (transaction FPVC), and then start the dunning proposal run again. If you run the dunning activity run in simulation mode, you can also test the correspondence creation. If you simulate a run again, but print after the first simulation run, in the second simulation the correspondence container is filled again and you can repeat the print. However, if you do not print between two simulation runs, the data in the correspondence container is overwritten and you can only print once at the end.
Activities End Dunning Procedure
Application component: Collections and Disbursements
App type: SAP GUI
Description:  The dunning end run ends running dunning procedures and is executed after payment receipts and master data changes (incoming payment method defined or dunning variant changed). Each process ensures that the associated dunning procedure is "marked" for ending (dunning trigger). The dunning end run checks the prerequisites and ends the dunning procedure if required.   If open items for a dunning procedure are included in an installment plan, this process ends the dunning procedure immediately, without any note. The dunning end run is not affected by this process.
Maintain Coinsurer Specifications
Application component: Collections and Disbursements
App type: SAP GUI
Description:   You define settings for the coinsurer, using those that identify the coinsurance shares from coinsurance-relevant premiums/claims, and costs for premiums/claims from policyholders that can be posted to the coinsurer.  These settings are represented by the coinsurance key. You can find out how to transfer the coinsurance key, under Posting Premiums, Claims and Costs .
Create Shipment
Application component: Transportation
App type: SAP GUI
Business roles: Customer Service Representative - Visit Management| Internal Sales Representative - Direct Store Delivery| Sales Manager - Direct Store Delivery
Customer Service Representative - Visit Management : 
Plans all the customer visits for the Direct Store Delivery business.

Internal Sales Representative - Direct Store Delivery : 
Ensures operations in the area of Direct Store Delivery.

Sales Manager - Direct Store Delivery : 
Is responsable for the whole Direct Store Delivery E2E process from plan to execute.
Change Shipment
Application component: Transportation
App type: SAP GUI
Business roles: Customer Service Representative - Visit Management| Internal Sales Representative - Direct Store Delivery| Sales Manager - Direct Store Delivery
Customer Service Representative - Visit Management : 
Plans all the customer visits for the Direct Store Delivery business.

Sales Manager - Direct Store Delivery : 
Is responsable for the whole Direct Store Delivery E2E process from plan to execute.

Internal Sales Representative - Direct Store Delivery : 
Ensures operations in the area of Direct Store Delivery.
Display Shipment
Application component: Transportation
App type: SAP GUI
Business roles: Customer Service Representative - Visit Management| Internal Sales Representative - Direct Store Delivery| Sales Manager - Direct Store Delivery
Sales Manager - Direct Store Delivery : 
Is responsable for the whole Direct Store Delivery E2E process from plan to execute.

Customer Service Representative - Visit Management : 
Plans all the customer visits for the Direct Store Delivery business.

Internal Sales Representative - Direct Store Delivery : 
Ensures operations in the area of Direct Store Delivery.
Create Output Condition Records - Sales
Application component: Output Determination
App type: SAP GUI
Business roles: Internal Sales Representative
Internal Sales Representative : 
Manages sales documents, e.g. captures changes or cancels sales orders, prepares quotations, and manages contracts. Monitors, troubleshoots, and collaborates on critical open issues from the sales order fulfillment process.
Change Output Condition Records - Sales
Application component: Output Determination
App type: SAP GUI
Business roles: Internal Sales Representative
Internal Sales Representative : 
Manages sales documents, e.g. captures changes or cancels sales orders, prepares quotations, and manages contracts. Monitors, troubleshoots, and collaborates on critical open issues from the sales order fulfillment process.
Display Output Condition Records - Sales
Application component: Output Determination
App type: SAP GUI
Business roles: Internal Sales Representative
Internal Sales Representative : 
Manages sales documents, e.g. captures changes or cancels sales orders, prepares quotations, and manages contracts. Monitors, troubleshoots, and collaborates on critical open issues from the sales order fulfillment process.
Create Ins. Obj. Int. Bal. Letter
Application component: Collections and Disbursements
App type: SAP GUI
Description:   A balance interest letter (correspondence type V030) contains all interest periods for an insurance object-business partner relationship, whose end lies between the dates of issue for the last and the current balance interest letters.
Bal. Int. Calc. History Ins. Obj.
Application component: Collections and Disbursements
App type: SAP GUI
Description:  You use the mass activity to execute balance interest calculation for a defined number of insurance objects (deposit contracts) with balance interest calculation. 
Key features:  For interest calculation for an insurance object, all items that exist and were actually posted for the analyzed combination of business partner, contract and currency are selected. The basis for balance interest calculation is always the balance from all items posted to an insurance object with balance interest calculation. If no balance interest calculation took place, or a posting was made in a period that lies before the first entry in the interest history, then interest calculation begins with the due date for the first item. If balance interest calculation has already taken place, interest is calculated on the basis of the last valid balance in the balance interest calculation history.  The interest periods are determined on the basis of the master data for the insurance objects, and using the selection criteria in the mass activity (see Determining Interest Periods). Note If you post items to an insurance object with balance interest calculation in a period for which interest has already been calculated, interest is recalculated for the period with the updated balance in the next balance interest calculation run. You can find more details in the section entitled Determining Interest Periods. That date from which an item goes to the balance is read from the value date for the G/L item. If this is empty, the due date for net payment for the subledger item is used. Only those items whose due date lies within the period for interest calculation, or that originate from the interest document for the last valid interest period, are required. The total for the interest amounts is then written to a table (VVKKISUMIOB), for each run, interval, company code, G/L account and currency. This table is also available in the simulation. This means that you can calculate interest on a yearly basis, and create values on a monthly basis for Controlling.
Balance Interest Calc. Ins. Object
Application component: Collections and Disbursements
App type: SAP GUI
Description:  You use the mass activity to execute balance interest calculation for a defined number of insurance objects (deposit contracts) with balance interest calculation. 
Key features:  For interest calculation for an insurance object, all items that exist and were actually posted for the analyzed combination of business partner, contract and currency are selected. The basis for balance interest calculation is always the balance from all items posted to an insurance object with balance interest calculation. If no balance interest calculation took place, or a posting was made in a period that lies before the first entry in the interest history, then interest calculation begins with the due date for the first item. If balance interest calculation has already taken place, interest is calculated on the basis of the last valid balance in the balance interest calculation history.  The interest periods are determined on the basis of the master data for the insurance objects, and using the selection criteria in the mass activity (see Determining Interest Periods). Note If you post items to an insurance object with balance interest calculation in a period for which interest has already been calculated, interest is recalculated for the period with the updated balance in the next balance interest calculation run. You can find more details in the section entitled Determining Interest Periods. That date from which an item goes to the balance is read from the value date for the G/L item. If this is empty, the due date for net payment for the subledger item is used. Only those items whose due date lies within the period for interest calculation, or that originate from the interest document for the last valid interest period, are required. The total for the interest amounts is then written to a table (VVKKISUMIOB), for each run, interval, company code, G/L account and currency. This table is also available in the simulation. This means that you can calculate interest on a yearly basis, and create values on a monthly basis for Controlling.
CurrChangeContractsAcctBalIntCalc.
Application component: Collections and Disbursements
App type: SAP GUI
Description:   You can execute a currency change for insurance objects with balance interest calculation using a mass activity, or online, if you are converting to the Euro, for instance. 
Key features:   During currency change, the open items for the selected insurance objects in the old currency are determined. Statistical items are then closed. Actual posted items that are relevant for interest calculation and actual posted items that are not relevant for interest calculation (additional receivables, for example) are then processed separately: The balances on the date of change are determined and written off. The currency is then changed for the contract account. Both balances are recalculated in the new currency (using the local currency as appropriate) and then reposted separately. The balances are posted to the reconciliation account defined in the Implementation Guide.  You can implement additional checks for the currency change in event V080 (sample module VVOZINS2_SAMPLE_V080 ).  In event V081 (sample module VVOZINS2_SAMPLE_V081 ), you can calculate charges for the currency change.  The following are prerequisites for currency changes:  You have calculated interest for the insurance object up to the day before the currency change. Note  Interest is calculated automatically online for the items on an insurance object, for which a currency change is to be executed. To execute a currency change in the mass activity, you have to have already calculated interest for the affected insurance objects in the balance interest calculation run.  No entries are permitted in the VVKKICLARIOB clarification table. If you post items in a period for which interest has already been calculated, an entry is created in this table. The old interest documents are reversed in the next interest run, and interest is recalculated.  On the insurance object, no items whose due date for net payment, posting date or value date lies on or after the date for the currency change, can exist in the old currency. Only reversed items are excepted from this rule.  If there are still open payment plan items in the old currency on the insurance object, a message informing you of this is output, but the currency change is still executed.
Create Balanced Contract Statements
Application component: Collections and Disbursements
App type: SAP GUI
Description:   A contract statement contains all open items and clearings for an insurance relationship, whose CPU date lies between the time of issue for the last contract statement and the time of issue for the current contract statement.  You can determine from the period delimitation how often a contract statement has been created. The system numbers and historically records the contract statements on an ongoing basis. 
Key features:   The date and time of issue are relevant for the creation of a contract statement.  If the date of issue is in the past, all items posted up until midnight of the previous day are shown on the account statement. The CPU date (central processing unit) on which the items were entered cannot be changed.  If the date of issue is the current date, all items posted on this date up to the CPU time are taken into account.  Balances on contract accounts are updated on the basis of the preceding contract statement.
Open Item Accounting Carryforward
Application component: Collections and Disbursements
App type: SAP GUI
Description:   The function enables you to clear items on an account managed on an open account basis. 
Key features:   You can execute open account clearing with or without balance carryforward. You can make your decision, for each contract account category, in the Implementation Guide.  Open account clearing without balance carryforward:  In clearing on an open account basis, those items that do not have a clearing restriction, or that have clearing restriction ‘D’, are selected. Statistical items are not entered. Credit and receivables, which belong to a contract account and have the same currency, are sorted according to their due date. The oldest items are cleared first. As far as possible, clearing is executed according to the sort, until all items are cleared. Clearing is also carried out in full for equal amounts with credit and receivables. If the credit exceeds the receivables, thus meaning that the credit can not be cleared in full, the last credit item required for clearing is only partially cleared (and vice versa). Just one clearing document is created, with the posting and document date for the posting parameters from the clearing on an open account basis. Posting area 1025 delivers the default values for the clearing reason and the document type.  Open account clearing with balance carryforward:  For open account clearing with balance carryforward, all items up to the to-date for the due date for net payment, or (if you have not filled that field) up to the system date, are cleared. Items for which interest has been calculated and items for which interest has not been calculated are dealt with separately, and are cleared with different documents. The documents created by open account clearing are then reposted on the following day: One document for each clearing, and one document for each balance carryforward, separated according to items with and without interest calculation (a maximum of four documents). The documents for the balance carryforwards have the main and subtransactions for posting area V065, separated according to items with and without interest calculation.
Contract Dun. Status
Application component: Collections and Disbursements
App type: SAP GUI
Description:   There is a specific insurance dunning history for SAP Insurance, in addition to the item-related dunning history. You can display all dunning procedures, which are and were executed for an insurance object-partner relationship or a contract account-partner relationship, in the insurance dunning history with the running dunning levels.  From the dunning history overview, you can display the documents that belong to the dunning groups, such as interest or charges documents, or the associated dunning lines.
Insurance Debit Entry
Application component: Collections and Disbursements
App type: SAP GUI
Description:   Mass activity (transaction VYSPA), which creates payment plan subitems and/or posts subledger documents – or executes debit entries - from payment plan items .   Dependent on the payment plan and payment plan item data for the insurance relationship, for which you execute a debit entry, the open items in question might be single items (if the payment plan item specifies a one-time payment of the total amount) or multiple open items. In the latter case, the open items match the partial amounts or installments (payment plan subitems) that result from the distribution specified by the payment plan key. Note Special feature when processing insurance relationships with customer-initiated payment form:  In the case of insurance relationships for which collection takes place on a customer-initiated basis, you cannot execute an "actual" debit entry until a payment has actually been received for this contract.