SAP ABAP IMG Activity PROD_PRO_BUKRS (Company Code-Dependent Settings for Product Type)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ FS-CML (Application Component) Loans Management
     ⤷ FTLC (Package) Customizing Treasury: Loan management
IMG Activity
ID PROD_PRO_BUKRS Company Code-Dependent Settings for Product Type  
Transaction Code S_ALR_87004708   IMG Activity: PROD_PRO_BUKRS 
Created on 19981222    
Customizing Attributes PROD_PRO_BUKRS   Company Code-Dependent Settings for Product Type 
Customizing Activity PROD_PRO_BUKRS   Company Code-Dependent Settings for Product Type 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PROD_PRO_BUKRS    

In this IMG activity you

  • Make settings for the product types already defined for each company code
  • Define the statuses per product type and company code
  • Define the possible status transfers per product type and company code

Settings for product types (company code-dependent):

Here you make both basic settings (which are fixed for the product type) and default settings (which are only proposals and can be modified in online mode). You also set the field control for loan master data. If you want to define field control for individual statuses, (application, offer, contract), you should not carry out this step until you define the statuses.

Basic settings:

  • Enter the number range you want to use for loan numbers. If you want to use number composition for number assignment, leave this field blank.
  • Enter the sample record no. range (Sample recNoRg) to be used for loan numbers for sample contracts.
  • If you want to assign the numbers using number composition, enter the number of characters of the loan number in the No. char. field.
  • In the CM period field define the period in years for which the cash flow is to written to the database.
  • In the FI posting field, define whether postings
    • are to be made in FI with customer accounts (enter 3)
    • are to be made in FI without customer accounts (enter 4)
      All other indicators are not supported in the loans area at present.
  • If the product type is to be posted to a customer account, define a dunning block.
  • Define the Discount limit.
  • If you intend to use the parallel position management functions, you must specify a general valuation class. You define the valuation class in the IMG for Treasury and Risk Management in the IMG step Define and Assign Valuation Classes.
  • For product types in product category 300, define whether you want to make use of the functions for decision-making (field Dec. active).
  • If you want the due date of conditions to be calculated on the basis of the start of the term of the condition rather than the calendar year, activate the Pmt meth. start indicator .
  • If you want to use payment details for this product type, activate the Payment details indicator. You can then use the following functions for the product type in the company code:
    • Maintenance of payment details for the loan or borrower's note order, including automatic default entries from the standing instructions for the business partner.
    • Cash Management update using the house bank specified in the payment details.
    • Replacement rule for the house bank in account determination using the bank specified in the payment details (see payment transaction for loans)
    • Generation of payment requests using the payment program for payment requests.
    • See also: Release note for payment details
  • The indicator price gains without proportionate gains from deferral write-back controls how price gains are calculated for product types where the price gain indicator is set to active.

    For more information see: Release note: Price gains with activated price gain indicator.

Default values for product type (company-code-dependent):

  • The values you define here are proposed as defaults when you create a loan but can be changed.

Define status per product type:

  • You create external statuses for each product type by assigning them to internal statuses. More than one external status can be assigned to an internal status. In online mode, you can manually make a status transfer to an internal status (change contract, change order, and so on.).
  • Using the status, you also define from which point in the process postings are allowed. To do this, enter the FI posting key you entered for the product type in the company code in the FI posting field. You are not allowed to enter a different key here. In the case of postings to customer accounts, the customer account is not created until this point. You should note that in connection with status transfers (see below), an unbroken status chain has to exist for the key you have set.
  • If you set the CG indicator (Generate cash flow in contract status before disbursement) for "contract" status, the system writes the cash flows for the loan contracts to the database without simulated disbursement flows. This cash flow contains the flows that have to be posted before the first disbursement, such as commitment interest or one-off charges.

    Note:

    This indicator only affects contract processing. No planned records are written to the database in the other loan statuses (application, offer).

    Effects of the CG indicator upon disbursement of the loan:

    • The release procedure is not active for disbursement:
      • The system writes all the flows that were generated when the first disbursement was entered, such as interest or repayments, to the database as planned records, regardless of the setting for the CG indicator.
    • The release procedure is active for disbursement and the CG indicator is set:
      • Before the disbursement is released, the system only writes the flows that have to be posted before the first disbursement to the database as planned records, such as commitment interest.
      When the disbursement is released, the system writes all the flows that were generated when the first disbursement was entered, such as interest and repayments, to the database as planned records.
    • The release procedure is active for disbursement and the CG indicator is not set:
      • Before the disbursement is released, no flows are written to the database.
      When the disbursement is released, the system writes all the flows that were generated when the first disbursement was entered to the database as planned records. As well as interest and repayments, these flows would also include commitment interest.
    • You enter one disbursement, but then delete it:
      • If the CG indicator is set, the system only writes the flows that have to be posted before disbursement, such as commitment interest and one-off charges, to the database as planned records.
  • If you want to have a field selection definition for a status different from the definition you made for the product type in a company code, you need to activate the indicator for alternative field selection (AFS) and make the field selection definitions for this status.

Define status transfers for product type:

  • In this step, you define the possible status transfers, for instance, from which external status you can change to which other status. If you want to be able to create a loan directly in one status, you should enter zero as the starting value for the old status.

Field selection:

  • You can define field selection for the loan master data for each product type in the company code. If you activate the Alternative field selection field in status maintenance, and branch from there to field selection maintenance, you can overwrite the settings for a particular product type and status.
  • Note the following:
    • If the Alternative field selection field is activated when you copy an application for a loan (using Copy from), all of the fields that have been set as 'hidden' fields in the field selection are automatically set to their initial value, in other words are reset to 0. For example, if in the "Settings for Product Type" on the Details screen you have set the actual principle (1 or 2) as default but in the field selection that is defined in the status you have set the field Planned/actual principle as a hidden field then when you copy an application the field Planned/actual principle is set to initial value, in other words, the planned principle 0 is set as default. Since the field is 'hidden' in the system application you can only change the default values in the IMG, in the 'Settings for Product Type on the Details screen.
    • The field selections for dunning can be overwritten by the settings in Customizing (if dunning is not set to active for a product type, for example, then all the fields are hidden).
    • For the external account statement and the interest certificate, the setting 'required entry' is considered as an 'optional entry', since the initial value '0' is a valid entry.
    • The settings for borrower's note orders must be made for contract status, and not for the statuses order execution
Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG PROD_PRO_BUKRS 0 HLA0100074 O HLA0100041  
SIMG PROD_PRO_BUKRS 1 O I070004705  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_PARTB C - View cluster SM34 DARLEHEN  
History
Last changed by/on SAP  19981222 
SAP Release Created in