SAP ABAP Data Element AD01PROFNR (Dynamic Item Processor Profile)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM-ISA (Application Component) Internet Sales
     AD01 (Package) B2R: Bapi Structures
Basic Data
Data Element AD01PROFNR
Short Description Dynamic Item Processor Profile  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type AD01PROFNR    
Data Type CHAR   Character String 
Length 8    
Decimal Places 0    
Output Length 8    
Value Table AD01C_PROF    
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID AD0  
Default Component name DLI_PROFILE   
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Profile 
Medium 15 DIP Profile 
Long 20 DIP Profile 
Heading 10 Profile 
Documentation

Definition

Name of the dynamic item processor profile (DI processor profile).

The dynamic item processor is a tool that the system uses to summarize data (for example, line items, totals records) into dynamic items in sales price calculation, resource-related billing, or data determination.

The DI profile controls how the system summarizes the data into dynamic items. A DI processor profile can have different usages.

Use

Examples

Dependencies

Supplementary Documentation - AD01PROFNR0001

Use

Enter a profile if you have selected results analysis type "B".

Procedure

Examples

Dependencies

Supplementary Documentation - AD01PROFNR0002

Use

Determining the DIP profile for service orders without a notification:

  • If there is no sales document item assigned to the service order, the DIP profile is copied from Customizing. Otherwise the DIP profile from the sales document item in the service order is used and cannot be changed there either.

Determining the DIP profile as well as the billing type when creating a service order with a notification:

Service orders without revenues:

  • If you create a notification together with an order, and if an automatic order seletion occurs in the notification, the DIP profile is copied from the selected order.
  • If an order does not exist, the system checks whether the order from the maintenance plan is stored in relation to the contract. If yes, the billing type and DIP profile is determined from the assigned contract.
  • If the DIP profile has not yet been filled, the Customizing settings are used.

Service orders with revenues:

  • The default value for the DIP profile from Customizing has the highest priority.
  • If there is no default value in Customizing, the value of the SD document that is assigned to message belonging to the corresponding order is used.
  • If a DIP profile is not available, and if the order was created from a maintenance plan with relation to the contract, a DIP profile from the contract item for the maintenance plan is used.

Dependencies

Example

Supplementary Documentation - AD01PROFNR0003

Use

Determining the DIP profile for service orders without a notification:

  • If there is no sales document item assigned to the service order, the DIP profile is copied from Customizing. Otherwise the DIP profile from the sales document item in the service order is used and cannot be changed there either.

Determining the DIP profile as well as the billing type when creating a service order with a notification:

Service orders without revenues:

  • If you create a notification together with an order, and if an automatic order seletion occurs in the notification, the DIP profile is copied from the selected order.
  • If an order does not exist, the system checks whether the order from the maintenance plan is stored in relation to the contract. If yes, the billing type and DIP profile is determined from the assigned contract.
  • If the DIP profile has not yet been filled, the Customizing settings are used.

Service orders with revenues:

  • The default value for the DIP profile from Customizing has the highest priority.
  • If there is no default value in Customizing, the value of the SD document that is assigned to message belonging to the corresponding order is used.
  • If a DIP profile is not available, and if the order was created from a maintenance plan with relation to the contract, a DIP profile from the contract item for the maintenance plan is used.

Dependencies

Example

History
Last changed by/on SAP  19991102 
SAP Release Created in